1 / 4

49th IETF Meeting

49th IETF Meeting. PILC Working Group Performance Enhancing Proxies Document. Changes from -03 to -04.

jenellew
Download Presentation

49th IETF Meeting

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. 49th IETF Meeting PILC Working Group Performance Enhancing Proxies Document 1

  2. Changes from -03 to -04 • Based on feedback we received at the Pittsburgh meeting, some changes were made to clarify the scope of the document (in particular, to indicate that the document primarily focuses on transport and application layer PEPs). • Flushed out the discussion of TCP ACK filtering and reconstruction and the discussion of priority-based multiplexing and filled in the section on protocol booster mechanisms (with help from Zach Shelby). • Filled in the holes in the examples sections. • Added some issues to the security considerations section which were not covered in the implications section. • Did a lot wordsmithing to make make formatting consistent and to make various sections easier to read. 2

  3. Changes from -03 to -04 • The most significant changes were made to the implications section… • Reworked (e.g. reworded and rearranged) the entire implications section to make the implications message clear. (Previously, the wording sometimes gave too much of an impression of “this is bad but maybe it doesn’t matter”.) • Filled in the end-to-end failure diagnostics implications section. • Added more detail to the implications for mobile hosts and implications re scalability sections. • Added some text re QoS and multi-homing implications along with a warning statement that this document does not profess to be complete re all of the possible implications of using PEPs. 3

  4. Status • The -04 draft was released in mid-October and went through working group last call. • We received only a few minor comments during last call. These were addressed in the -05 draft released just before the deadline for the San Diego meeting. • The most significant ([opinion] not really that significant) changes to the -05 draft were: • The addition of a statement indicating that PEPs are often used with existing link layers which cannot benefit from the advice in the ADVICE document. This was an obvious statement previously missing; • The addition of a statement indicating possible implications re the interaction of PEP based QoS mechanisms and DiffServ. • The rest of the changes were wording or formatting corrections. 4

More Related