1 / 5

Layer 1 VPNs

Layer 1 VPNs. draft-takeda-l1vpn-applicability-00.txt Adrian Farrel (Olddog Consulting) Hamid Ould-Brahim (Nortel Networks) Dimitri Papadimitriou (Alcatel) Tomonori Takeda (NTT). draft-takeda-l1vpn-framework-01.txt Raymond Aubin (Nortel) Marco Carugi (Nortel) Ichiro Inoue (NTT)

lucian
Download Presentation

Layer 1 VPNs

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. Layer 1 VPNs draft-takeda-l1vpn-applicability-00.txt Adrian Farrel (Olddog Consulting) Hamid Ould-Brahim (Nortel Networks) Dimitri Papadimitriou (Alcatel) Tomonori Takeda (NTT) draft-takeda-l1vpn-framework-01.txt Raymond Aubin (Nortel) Marco Carugi (Nortel) Ichiro Inoue (NTT) Hamid Ould-Brahim (Nortel) Tomonori Takeda (NTT) 60th IETF San Diego August 2004

  2. Summary of Status • Framework ID submitted before the last IETF meeting • in line with liaison from ITU-T SG13 • for better understanding and further cooperation between two bodies • Significant interest in L1VPNs in CCAMP • Currently, still progressing “under the care of CCAMP” • Based on mailing list discussion, Framework ID updated (next page) • And Applicability ID submitted (second next page) • to show how existing GMPLS-based techniques can be used to support L1VPNs • to show deltas from existing GMPLS-based techniques • Note: a new mailing list is set up for L1VPNs 60th IETF San Diego August 2004

  3. Framework ID • Updates in 01 version • Incorporated comments received • Added new/different terminologies (section 2) • Reorganized service models for clarification (Virtual Node, Virtual Link, Per VPN Peer) (section 7.3) • Added requirement details according to ITU-T SG13 documents (section 8) • Editorial enhancements • Remaining issues • No further known major issues • Some issues • Refine terminologies • Security section • Further review comments solicited 60th IETF San Diego August 2004

  4. Applicability ID • Applicability of existing GMPLS techniques to L1VPNs • GVPN - draft-ouldbrahim-ppvpn-gvpn-bgpgmpls-05.txt • GMPLS Overlay - draft-ietf-ccamp-gmpls-overlay-04.txt • Summary • Most requirements are covered by existing drafts • Identified 7 items for possible additional work (some are optional) • Resource management: per VPN resource management, shared restoration/extra traffic within a VPN or among VPNs • Tunnel mechanisms/auto-discovery • MIB modules: SPC (Soft Permanent Connection) support • etc. • Remaining issues • More details (e.g., detailed applicability to Per VPN Peer Service Model) • Solicit feedback 60th IETF San Diego August 2004

  5. Next Steps • Continue to discuss L1VPNs on special mailing list • Regular status updates to CCAMP mailing list • Propose to adopt L1VPNs as a new CCAMP charter item • High level of interest (around 100 subscribers to the mailing list) • Most of requirements work already done (in ITU-T and here) • Protocol work is expected to be relatively minor (most requirements are already covered by existing drafts). • Coordination with other bodies (e.g., ITU-T) • Start to discuss protocol extensions based on applicability ID as a baseline. • Please sign up for the L1VPN mailing list, and give us feedback on the drafts • https://www1.ietf.org/mailman/listinfo/l1vpn 60th IETF San Diego August 2004

More Related