RE: hop-by-hop and router alert options

2004-08-26 Thread Pekka Savola
Thanks for your reasonable note, Hannes. On Wed, 25 Aug 2004, Tschofenig Hannes wrote: - there have been a number of discussions about the bandwidth broker concept in the past and the disadvantages are known. (my personal opinion) if it boils down to the protocol details then the difference

Options for IETF administrative restructuring

2004-08-26 Thread Leslie Daigle
[This is a re-send of a message I sent last night; that message is caught in the list moderation queue because the attachment put it over the message size limit. It should appear on the list... sometime. The Internet-Draft may appear in the archive before then. In the meantime, there are

Re: Options for IETF administrative restructuring

2004-08-26 Thread John C Klensin
Leslie and Harald, I would like to make one suggestion about this process. For suggestions about substance, I will, of course, wait for the final -00 version of the draft. This note is deliberately being sent before I have done so because I don't want my remarks to be biased by how I feel

Re: hop-by-hop and router alert options

2004-08-26 Thread Michael Welzl
Hi folks, I would just like to add that our studies are ongoing, and this: variety of Internet paths. It observes that on average, IP options introduce between 7% and 26% (for different sets of paths at different times) of additional delay. The article says that In any case, the additional

I-D ACTION:draft-malamud-consultant-report-00.txt (fwd)

2004-08-26 Thread Harald Tveit Alvestrand
It seems that the I-D publication process is faster than the process of sending large messages to the IETF list. Have a good read! Harald -- Forwarded Message -- Date: 26. august 2004 15:34 -0400 From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: I-D

Re: hop-by-hop and router alert options

2004-08-26 Thread Iljitsch van Beijnum
On 26-aug-04, at 8:13, Pekka Savola wrote: But what I'm really worried about is that IP router alert -like options are options which a hardware implementation cannot process. An attacker can just specify an undefined router alert option which forces the processing to go to the slow path (instead

WG Action: Conclusion of Internet Printing Protocol (ipp)

2004-08-26 Thread The IESG
The Internet Printing Protocol (ipp) in the Application Area has concluded. The IESG contact persons are Ted Hardie and Scott Hollenbeck. The mailing list will remain active. +++ The Internet Printing Protocol (IPP) working group has concluded. The group was chartered to develop requirements

WG Action: Conclusion of Internet Printing Protocol (ipp)

2004-08-26 Thread The IESG
The Internet Printing Protocol (ipp) in the Application Area has concluded. The IESG contact persons are Ted Hardie and Scott Hollenbeck. The mailing list will remain active. +++ The Internet Printing Protocol (IPP) working group has concluded. The group was chartered to develop requirements

Document Action: 'IPv6 Enterprise Network Scenarios' to Informational RFC

2004-08-26 Thread The IESG
The IESG has approved the following document: - 'IPv6 Enterprise Network Scenarios ' draft-ietf-v6ops-ent-scenarios-05.txt as an Informational RFC This document is the product of the IPv6 Operations Working Group. The IESG contact persons are David Kessens and Bert Wijnen. RFC Editor Note:

Protocol Action: 'Source-Specific Protocol Independent Multicast in 232/8' to BCP

2004-08-26 Thread The IESG
The IESG has approved the following document: - 'Source-Specific Protocol Independent Multicast in 232/8 ' draft-ietf-mboned-ssm232-08.txt as a BCP This document is the product of the MBONE Deployment Working Group. The IESG contact persons are David Kessens and Bert Wijnen. Technical

Last Call: 'RTP Payload Formats for European Telecommunications Standardsv Institute (ETSI) European Standard ES 202 050, ES 202 211, and ES 202 212 Distributed Speech Recognition Encoding' to Propo

2004-08-26 Thread The IESG
The IESG has received a request from the Audio/Video Transport WG to consider the following document: - 'RTP Payload Formats for European Telecommunications Standards Institute (ETSI) European Standard ES 202 050, ES 202 211, and ES 202 212 Distributed Speech Recognition Encoding '

Document Action: 'EAP Method Requirements for Wireless LANs' to Informational RFC

2004-08-26 Thread The IESG
The IESG has approved the following document: - 'EAP Method Requirements for Wireless LANs ' draft-walker-ieee802-req-04.txt as an Informational RFC This document has been reviewed in the IETF but is not the product of an IETF Working Group. The IESG contact person is Margaret Wasserman.