From: Gonzalo Camarillo = <Gonzalo.Camarillo@ericsson.= com>Subject: [RAI] Fwd: NOMCOM 2013 - UPDATED 2nd Call for = Nominations - APP, OAM, RAI, TSVDate: October 11, 2013 = 2:44:23 AM EDTTo: <rai@ietf.org>Folks,
we need more volunteers (see email below). If you are = thinking of
running but still have some doubts about it, feel free to = talk with me
(or with any of the former RAI ADs) and we will be happy = to clarify
everything for = you.
Cheers,
Gonzalo
-------- Original Message = --------
Subject: NOMCOM 2013 - UPDATED 2nd Call for Nominations - = APP, OAM, RAI, TSV
Date: Tue, 8 Oct 2013 11:45:14 -0700
From: = NomCom Chair <nomcom-chair@ietf.org>
Rep= ly-To: <nomcom-chair-2013@ietf.org&= gt;
To: IETF Announcement List <ietf-announce@ietf.org>
C= C: <ietf@ietf.org>
UPDATE: = nominations are too sparse in several of the IESG areas: APP, = OAM,
RAI, and TSV. If you know one or more of those areas, = exercise your social
network and submit nominations. We'll be = very grateful!
Is there someone you work with at IETF who has = leadership potential and a
growing track record? Please read this = Nomcom call for nominations and
consider
nominating her or him. Or = several folks! Deadline for nominations is
October 18.
Nominate = soon to give your nominee(s) plenty time to fill in = the
questionnaire.
If you're nominated, even if you support = the present incumbent, being
reviewed
by Nomcom is great IETF = experience. The questionnaire offers a chance to
think about = IETF and about your area. Whether or not your = candidacy
progresses
this time, you'll have gained some valuable = insights, and you'll have
contributed
greatly. This process only = works because many IETFers take part; please
join in.
Lots = more, including which positions are open, how to make a = nomination
(including nomination of yourself), and how to send us = your feedback on
the desired expertise, follows.
IETFers, = let's hear from you! Make nominations, accept = nominations!
If you have any questions about the process, feel = free to get in touch
with me.
Best regards,
Allison for = the Nomcom
Allison Mankin
Nomcom Chair 2013-14
----- = The Info You Need for Nominating -----
The 2013-14 Nominating = Committee (Nomcom) is seeking nominations
from now until October 18, = 2013. The open positions being considered
by this year's Nomcom can = be found later in this section, and also on
this year's Nomcom = website:
https://datatracker.iet= f.org/nomcom/2013/
Information about the desired expertise = for positions is here:
= https://datatracker.= ietf.org/nomcom/2013/expertise
Nominations may be made by = selecting the Nominate link at the top of
the Nomcom 2013 home page, = or by visiting the following = URL:
https://datatracker.ietf.org/nomcom/2013/nominate/
Note= that nominations made using the web tool require an = ietf.org
datatracker account. You can create a datatracker ietf.org = account
if you don't have one already by visiting the following = URL:
https://datatracker.ietf.org/accounts/create/
Nominatio= ns may also be made by email to nomcom13 at ietf.org.
If you nominate = by email, please include the word "Nominate" in the Subject
and = indicate in the email who is being nominated, their email address = (to
confirm acceptance of the nomination), and the position for which = you
are making the nomination. If you use email, please use a = separate email for
each person you nominate, and for each position = (if you are nominating one
person for multiple = positions).
Self-nomination is welcome! No need to be = shy.
Nomcom 2013-14 will follow the policy for "Open Disclosure = of Willing
Nominees" described in RFC 5680. As stated in RFC = 5680: "The list of
nominees willing to be considered for positions = under review in the
current Nomcom cycle is not confidential". = Willing nominees for each
position will be listed in a publicly = accessible way - anyone with a
datatracker account may access the = lists. In all other ways, the
confidentiality requirements of = RFC 3777/BCP10 remain in effect. All
feedback and all Nomcom = deliberations will remain confidential and will
not be = disclosed.
In order to ensure time to collect sufficient = community feedback about
each of the willing nominees, nominations = must be received by the
Nomcom on or before October 18, 2013. = Please submit your nominations
as early as possible for the = sake of your nominees, as we've set the
questionnaire submission = deadline for October 25, 2013.
The list of people and posts whose = terms end with the March 2014 IETF
meeting,
and thus the positions = for which we are accepting nominations:
IAOC
Chris = Griffiths
IAB
Bernard Aboba
Marc Blanchet
Ross = Callon
Eliot Lear
Hannes Tschofenig
IESG
Barry Leiba = (Applications)
Brian Haberman (Internet)
Benoit Claise (Operations = and Management)
Gonzalo Camarillo (RAI)
Stewart Bryant = (Routing)
Sean Turner (Security)
Martin Stiemerling = (Transport)
Please be resourceful in identifying possible = candidates for these
positions, as developing our talent is a very = crucial requirement for
the IETF. Also, please give serious = consideration to accepting nominations
you receive.
The = summaries of the desired expertise for the positions, developed by = the
respective bodies, are found = at:
https://datatracker.ietf.org/nomcom/2013/expertise/
In = addition to nominations, the Nomcom seeks community input on
the = positions themselves. We need and welcome the community's
views = and input on the jobs within each organization. If you
have ideas on = the positions' responsibilities (more, less,
different), please let = us know. You can send us email about this to
nomcom13 at = ietf.org, and we will use this feedback actively.
Thank you for = your help in nominating a great pool of strong and = interesting
nominees!
__________________________________= _____________
RAI mailing = list
RAI@ietf.org
https://www.ietf.org/mailman/listinfo/rai
--------- Original Message -----= ------=_09d01da8832482feef822c9b09c67cf6-- From michaelc@idssoftware.com Sat Oct 19 06:19:41 2013 Return-Path:Subject: [P2PSIP] Broken Stop and Wait Algorithm?
From: "Roland B= less" <roland.bless@kit.edu>
Date: 10/18/13 12:46 pm
To: "P= 2PSIP WG" <p2psip@ietf.org>
Hi all,
while imp= lementing more of the RELOAD protocol we came across
the following is= sue:
In sec. 6.6.3.1. Stop and Wait Sender Algorithm
htt= p://tools.ietf.org/html/draft-ietf-p2psip-base-26#section-6.6.3.1
the spec says:
For each retransmission, the sequence number MUST = be incremented.
Retransmissions continue until a response is r= eceived, or until a
total of 5 requests have been sent or there has b= een a hard ICMP
error [RFC1122] or a TLS alert. The sender knows a re= sponse was
received when it receives an ACK with a sequence number th= at
indicates it is a response to one of the transmissions of this
messages.
This would cause potential duplicates at t= he receiving side:
A B
---------> FramedMsg #1 ------= -> ---> deliver FramedMsg #1
|*drop* <-- Ack #1 >&= lt;----------
(A: timeout
+ retransmit)
---= ------> FramedMsg #2 -------> ---> deliver FramedMsg #2
(sam= e as above, i.e.
*duplicate*).
<----------- Ack #2 ><-= ----------
(A: ack received,
transmit next frame)
=
---------> FramedMsg #3 -------> ---> deliver FramedMsg #3<= br />
Given the current scheme, the receiver cannot
distinguis= h between the retransmitted frame (#2) and
a new one (#3). What was t= he reason to use _new_ sequence numbers
for retransmissions? Unless y= ou increment the
sequence number by more than 5 for each _new_
= frame, the receiving side could not filter out
duplicates.
Did I miss something?
Regards,
Roland
_________= ______________________________________
P2PSIP mailing list
P2PS= IP@ietf.org
https://www.ietf.org/mailman/listinfo/p2psip
Dear P2PSIP =
Members:
I am seeking some information about P2PSIP =
products/prototypes developed by researchers and/or =
vendors.
Any information related to the P2PSIP products will be =
extremely helpful.
I will =
appreciate any information related to this sent to me via =
email.
This is my personal enquiry for obtaining the info =
about the latest status related to the P2PSIP products.
If needed, =
anyone can call me as well.
Thanks in =
advance.
Best regards,
Radhika R. =
Roy
A&S
U.S. Army RDECOM CERDEC =
S&TCD
6010 Frankford St, =
C2/CNT East, Room 402-44
Aberdeen Proving Ground, =
MD 21005-5001
Tel (office): =
443-395-7400
DSN:648-7400
Email: radhika.r.roy.civ@mail.mil=
PS: If any procurement is done, it follows the normal =
official procedures.