1 / 5

End-to-end Extension for PCN Encoding draft-menth-pcn-e2e-encoding-00

End-to-end Extension for PCN Encoding draft-menth-pcn-e2e-encoding-00. Michael Menth University of Wuerzburg Jozef Babiarz Nortel Networks. Toby Moncaster BT. Note.

mavis
Download Presentation

End-to-end Extension for PCN Encoding draft-menth-pcn-e2e-encoding-00

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. End-to-end Extension for PCN Encodingdraft-menth-pcn-e2e-encoding-00 Michael Menth University of Wuerzburg Jozef Babiarz Nortel Networks Toby Moncaster BT draft-menth-pcn-e2e-encoding-00 PCN WG, 72nd IETF

  2. Note • This draft looks at problems that are out of scope of current charter but are important for possible evolution of PCN as they impact selection for encoding. draft-menth-pcn-e2e-encoding-00 PCN WG, 72nd IETF

  3. Baseline Encoding vs. End-to-end Extension for PCN Encoding • Issue • Baseline encoding proposes the use of ECN field of the Voice-Admit DSCP for PCN only inside the PCN-domain and for ECN use outside the PCN-domain. • We propose that to be able to support end-to-end extension for PCN encoding, the ECN field of the DSCP that is used to mark PCN-traffic (possibly Voice-Admit DSCP) uses alternate ECN semantics. draft-menth-pcn-e2e-encoding-00 PCN WG, 72nd IETF

  4. Motivation for e2e PCN • Motivation • Real-time applications like VoIP require QoS assurance end-to-end. • Define encoding method that can support possible evolution of PCN across multiple domains and end-to-end in controlled environments. • Idea • ECN semantics (RFC 3168) do NOT apply to the Voice-Admit DSCP • Voice-Admit DSCP uses newly defined semantics for the ECN field possible as defined in draft-menth-pcn-psdm-encoding • RFC 4774 in Section 3.1 suggests the above as viable approach for defining alternate semantics for ECN field • No dropping is required of “11” market packets at the PCN-domain edges • No remarking of ECN field on egress from PCN domain • e2e PCN potentially used for rate adaptation, etc. draft-menth-pcn-e2e-encoding-00 PCN WG, 72nd IETF

  5. Request • PCN WG as that an DSCP be assigned to which ECN semantics as defined in RFC 3168 do not apply. • Possible candidate could be the Voice-Admit DSCP. (draft-ietf-tsvwg-admitted-real-time-dscp) • At a later time, PCN WG could define new semantics that could be used for PCN and applied it to the new DSCP. • Comments! draft-menth-pcn-e2e-encoding-00 PCN WG, 72nd IETF

More Related