1

draft-levy-idr-6pe-survey-00.txt

Francois Le Faucheur - flefauch@cisco.com

Eric Levy-AbegnoliFrancois Le Faucheur

Cisco Systems

Rajiv Papneja Isocore

6PE (IPv6 over IPv4 MPLS)- Implementation Report

222

5 Responses to 6PE Implementation Survey

• two router implementations:

- Cisco Systems

- Juniper Networks

• three implementations on network test equipments:

- Ixia

- Agilent

- Spirent

333

Compliance Statements

• MUSTsAll the implementations comply with all the “MUSTs"

• SHOULDs/MAYsImplementations on test equipment also supports all (or all but one) "SHOULDs"/"MAYs"

• LABEL ALLOCATION STRATEGY: Cisco implementation allocates and advertises an arbitrary label

Juniper implementation allocates IPv6 Explicit NULL label

Both implementation comply with the [6PE] “MUST” to accept both forms of advertisement

Both Implementations interoperate

444

Interop Testing

• Basic interoperability between Cisco, Juniper and Ixia has been successfully tested as part of an ISOCORE interop event

See section 3 for details on scope of tests

555

Any Issues Identified?

• No issues identified with 6PE spec

(like ambiguity, holes,..)

• One point brought to light :

while case (b) of inter-AS operations is applicable when arbitrary labels are used, case (b) is not applicable in the case where IPv6 Explicit-Null is used

because in that case, it does not result in the use of inter-AS LSPs from ingress 6PE to egress 6PE allowing label switching at every hop including ASBRs. Rather, it results in IPv6 lookup and IPv6 forwarding at the ASBRs.

666

Next Steps

• This was a necessary step to allow 6PE to move to RFC (as per Routing Area rules)

• let that draft die its natural death