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

pwe3 protocol layering
SMART_READER_LITE
LIVE PREVIEW

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


slide-1
SLIDE 1

1

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>

slide-2
SLIDE 2

2 Bryant PWE3 Protocol layering

Forwarder

Single PW IWF Instance Single PW IWF Instance Single PW IWF Instance Multipoint PW IWF Instance NSP NSP NSP NSP PW Instance PW Instance PW Instance Multipoint PW Instance PWES PWES PWES PWES

PE Device

Forwarder

Forwarder introduced at request of PPVPN

slide-3
SLIDE 3

3 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)?

slide-4
SLIDE 4

4 Bryant PWE3 Protocol layering

IP PSN

+---------------------------+ | Payload | +---------------------------+ | Payload Convergence | +---------------------------+ | Timing | +---------------------------+ | Sequencing | +---------------------------+ | PW Identification | +---------------------------+ | PSN Convergence |

  • ---------------------------+

| PSN | +---------------------------+ | MAC/Data-link | +---------------------------+ | Physical | +---------------------------+ +---------------------------+ | Raw payload when possible | +---------------------------+ | As Needed | +---------------------------+ | RTP | +-------------+ | | | | | +-------------+ | L2TP, GRE, IPSec, MPLS etc| +---------------------------+ | Not needed |

  • ---------------------------+

| IP | +---------------------------+ | MAC/Data-link | +---------------------------+ | 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

  • n the PW)
slide-5
SLIDE 5

5 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 | +---------------------------------------------+ | Inner Label | +---------------------------------------------+ | Outer Label | +---------------------------------------------+

Is the CW sufficiently generic?

slide-6
SLIDE 6

6 Bryant PWE3 Protocol layering

Fragmentation

Fragmentation section will be updated to harmonise with <draft-malis-pwe3-fragmentation-00.txt>

slide-7
SLIDE 7

7 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
  • versight by an MPEG/DVB expert.
slide-8
SLIDE 8

8 Bryant PWE3 Protocol layering

Terminology

Many of the PWE3 documents include a terminology section, and none of them agree

  • n 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?

slide-9
SLIDE 9

9 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.

slide-10
SLIDE 10

10 10 10 Bryant PWE3 Protocol layering

PPVPN L2VPN L3VPN

Work Dependencies

L2TP MPLS Needs work Not fully synced up? Other Encap Not needed ? RTP Ext’ns PWE3 Real time RTP