PWE3 Protocol Layering PWE3 IETF-54 July 15, 2002 Stewart Bryant - PowerPoint PPT Presentation

PWE3 Protocol Layering PWE3 IETF-54 July 15, 2002 Stewart Bryant <stbryant@cisco.com> Danny McPherson <danny@tcb.net> Mark Townsley <mark@townsley.net> Lloyd Wood <lwood@cisco.com> 1

Forwarder PE Device PWES PW Instance Single PW IWF NSP Instance PWES PW Instance Single PW IWF NSP Instance Forwarder PWES PW Instance Single PW IWF NSP Instance PWES Multipoint PW IWF Multipoint NSP Instance PW Instance Forwarder introduced at request of PPVPN 2 Bryant PWE3 Protocol layering

PSN Stacks • Should the PSN stack diagrams Fig10 and Fig 11 be retained in the text, or should they be relegated to appendices (follows from question to list)? • Is the MPLS CW sufficiently generic for this text (it hails from Martini, but does not specify bit allocations or sizes)? 3 Bryant PWE3 Protocol layering

IP PSN +---------------------------+ +---------------------------+ | Payload | | Raw payload when possible | +---------------------------+ +---------------------------+ | Payload Convergence | | As Needed | +---------------------------+ +---------------------------+ | Timing | | RTP | +---------------------------+ +-------------+ | | Sequencing | | | | +---------------------------+ | +-------------+ | PW Identification | | L2TP, GRE, IPSec, MPLS etc| +---------------------------+ +---------------------------+ | PSN Convergence | | Not needed | ----------------------------+ ----------------------------+ | PSN | | IP | +---------------------------+ +---------------------------+ | MAC/Data-link | | MAC/Data-link | +---------------------------+ +---------------------------+ | Physical | | Physical | +---------------------------+ +---------------------------+ Do we need to retain GRE and IPSEC as tunnel types? Is anyone using/planning to use them for PW? Can they be dropped from the PW design? (Note that L2TP and GRE/MPLS could run over IPSec with no impact on the PW) 4 Bryant PWE3 Protocol layering

MPLS PSN +---------------------------+ | Payload | +---------------------------+ | Payload Convergence | +---------------------------+ | Timing | +---------------------------+ | Sequencing | +---------------------------+ | PW Identification | +---------------------------+ | PSN Convergence | ----------------------------+ | PSN | +---------------------------+ | MAC/Data-link | +---------------------------+ | Physical | +---------------------------------------------+ +---------------------------+ | Rsvd | Flags |0 0| Length | Sequence Number | +---------------------------------------------+ Is the CW sufficiently generic? | Inner Label | +---------------------------------------------+ | Outer Label | +---------------------------------------------+ 5 Bryant PWE3 Protocol layering

Fragmentation Fragmentation section will be updated to harmonise with <draft-malis-pwe3-fragmentation-00.txt> 6 Bryant PWE3 Protocol layering

TDM and Cell • Payload Type section (3.3) could use some help from the TDM, SONET and Cell teams. (TDM Requirements?) • Document could also do with some oversight by an MPEG/DVB expert. 7 Bryant PWE3 Protocol layering

Terminology Many of the PWE3 documents include a terminology section, and none of them agree on terms. Options: One of the architecture docs contains the master copy and other docs only define terms that are unique to their scope PWE3. A separate terminology draft is written and all other documents remove non-unique terms. What should we do? 8 Bryant PWE3 Protocol layering

Framework There is a high degree of overlap between the framework document and the protocol layering document. Options: 1) Framework folded into PLD. 2) Framework references PLD and deletes overlapping text unless needed to clarify a point. 9 Bryant PWE3 Protocol layering

Work Dependencies PPVPN L2VPN L3VPN PWE3 Not fully synced up? Real time Not needed ? RTP Ext’ns L2TP RTP Other Encap MPLS Needs work 10 10 10 Bryant PWE3 Protocol layering