1 / 10

UDP PWs draft-stein-pwe3-udp-00.txt

UDP PWs draft-stein-pwe3-udp-00.txt. PWE3 – 60 th IETF 2 August 2004. Yaakov (J) Stein. Issues. UDP/IP based PWs in PWE3 architecture/architecture UDP/IP extensively deployed in TDM PWs UDP/IP PWs useful alternative in enterprise space

hisa
Download Presentation

UDP PWs draft-stein-pwe3-udp-00.txt

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. UDPPWsdraft-stein-pwe3-udp-00.txt PWE3 – 60th IETF 2 August 2004 Yaakov (J) Stein

  2. Issues UDP/IP based PWs in PWE3 architecture/architecture UDP/IP extensively deployed in TDM PWs UDP/IP PWs useful alternative in enterprise space Resolution of issue requested by ITU-T SG13 in liaison Open Questions: • Where should PW label be placed? • What label distribution mechanism should be used?

  3. Placement Only specific suggestion has been in TDMoIP draft • destination UDP port number = registered value • source UDP port number = PW label Alternative 1 • some mechanism to distinguish PWs • destination UDP port number = PW label Alternative 2 • destination UDP port number = registered value • additional MPLS-like label after UDP/IP headers

  4. Constraint – NAT/firewalls use of constant, known destination port number allows transversal of port translation devices and firewalls IP address, port number IP address TDMoIP server

  5. Label distribution src=P dest=W implicit distribution explicit distribution via PWE control protocol W registered port # initiator src=Q dest=P src=P dest=Q label map P label map Q src=Q dest=P src=Pdest=Q

  6. Need Immediate Decisions Request WG to decide: • Where should we put PW labels for UDP/IP ? • What label distribution method should we use ?

  7. TDMoIPfinal (?)Updatesdraft-ietf-pwe3-tdmoip-01.txt PWE3 – 60th IETF 2 August 2004 Yaakov (J) Stein

  8. TDM TDM TDM PW TDM trail TDM trail X trunk conditioning AIS no TDM OAM transferred RDI TDM trail L TDM PW TDM TDM X AIS R TDM OAM transferred but not necessarily in native format RDI TDMoIP Defect OAM data only (N*DS0) Two scenarios for structure-aware TDM: Trail terminated Trail extended (as in SAToP) Trail – ITU term for data + defect/performance OAM AIS - forward defect indication generated by any node, propagated to client layers RDI - reverse defect indication generated only by trail termination, not propagated up Trunk conditioning – forward defect of individual DS0

  9. TDMoIP Performance OAM Purpose: • monitor backup PWs • assist advanced clock recovery in CBR-intensive environment Functionality: • connectivity verification • round trip delay measurement • PDV measurement Mechanisms: • VCCV in same PW • separate OAM PW in same tunnel

  10. Final corrections before LC • Remove FORMID field (per draft-bryant-mcpherson-pwe3-cw) • Comply with WG decisions regarding UDP/IP ports • Finish specification of VCCV performance OAM mode

More Related