Skip to main content

Unicast UDP Usage Guidelines for Application Designers
draft-ietf-tsvwg-udp-guidelines-11

Yes

(Magnus Westerlund)

No Objection

(Chris Newman)
(Dan Romascanu)
(David Ward)
(Jon Peterson)
(Mark Townsley)
(Ron Bonica)
(Ross Callon)
(Russ Housley)
(Tim Polk)

Recuse

(Lars Eggert)

Note: This ballot was opened for revision 11 and is now closed.

Jari Arkko Former IESG member
Yes
Yes (2008-08-14) Unknown
I don't quite understand how the tracker brought this document to the
telechat without having Magnus vote "Yes". Presumably Magnus is happy
with the document, no?
Magnus Westerlund Former IESG member
Yes
Yes () Unknown

                            
Chris Newman Former IESG member
No Objection
No Objection () Unknown

                            
Cullen Jennings Former IESG member
(was Discuss) No Objection
No Objection (2008-08-13) Unknown
I'd really like to talk a little bit about the MSL - the implementation I see code for a MSL much shorter than the 2 minutes recommended here. The result is that it's very hard to predict how long anything will wait. We would be much better off to revise the MSL to some realistic number - then people might implement that and one would count on it. All you can count on today is that if you have a MSL of 2 minutes, lots of equipment will time out long before that.
Dan Romascanu Former IESG member
(was Discuss) No Objection
No Objection () Unknown

                            
David Ward Former IESG member
(was Discuss) No Objection
No Objection () Unknown

                            
Jon Peterson Former IESG member
No Objection
No Objection () Unknown

                            
Lisa Dusseault Former IESG member
No Objection
No Objection (2008-09-11) Unknown
Section 3.4:
   "This results in a relatively weak
   protection from in terms of coding theory"

I think some noun is missing after the word "from"

Same section:

   "This check is not strong from a coding or cryptographic
   perspective, and is not designed to detect physical-layer errors or
   malicious modification of the datagram"

Is it that it can't detect or can't distinguish between?
Mark Townsley Former IESG member
No Objection
No Objection () Unknown

                            
Pasi Eronen Former IESG member
No Objection
No Objection (2008-08-11) Unknown
There's some repetition of text in Sections 3.1.2 and 3.5, but
presumably RFC editor copyediting will take care of that.
Ron Bonica Former IESG member
No Objection
No Objection () Unknown

                            
Ross Callon Former IESG member
No Objection
No Objection () Unknown

                            
Russ Housley Former IESG member
No Objection
No Objection () Unknown

                            
Tim Polk Former IESG member
No Objection
No Objection () Unknown

                            
Lars Eggert Former IESG member
Recuse
Recuse () Unknown