< draft-mirsky-6man-unified-id-sr-01.txt   draft-mirsky-6man-unified-id-sr-02.txt >
Network G. Mirsky Network G. Mirsky
Internet-Draft ZTE Corp. Internet-Draft ZTE Corp.
Intended status: Standards Track P. Shaofu Intended status: Standards Track P. Shaofu
Expires: April 13, 2019 ZTE Corporation Expires: October 5, 2019 ZTE Corporation
October 10, 2018 April 3, 2019
Unified Identifier in IPv6 Segment Routing Networks Unified Identifier in IPv6 Segment Routing Networks
draft-mirsky-6man-unified-id-sr-01 draft-mirsky-6man-unified-id-sr-02
Abstract Abstract
Segment Routing architecture leverages the paradigm of source Segment Routing architecture leverages the paradigm of source
routing. It can be realized in a network data plane by prepending routing. It can be realized in a network data plane by prepending
the packet with a list of instructions, a.k.a. segments. A segment the packet with a list of instructions, a.k.a. segments. A segment
can be encoded as a Multi-Protocol Label Switching (MPLS) label, IPv4 can be encoded as a Multi-Protocol Label Switching (MPLS) label, IPv4
address or IPv6 address. Segment Routing can be applied in MPLS data address or IPv6 address. Segment Routing can be applied in MPLS data
plane by encoding segments in MPLS label stack. It also can be plane by encoding segments in MPLS label stack. It also can be
applied to IPv6 data plane by encoding list of segment identifiers in applied to IPv6 data plane by encoding list of segment identifiers in
skipping to change at page 1, line 40 skipping to change at page 1, line 40
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on April 13, 2019. This Internet-Draft will expire on October 5, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 6, line 8 skipping to change at page 6, line 8
8. Normative References 8. Normative References
[I-D.bryant-mpls-unified-ip-sr] [I-D.bryant-mpls-unified-ip-sr]
Bryant, S., Farrel, A., Drake, J., and J. Tantsura, "MPLS Bryant, S., Farrel, A., Drake, J., and J. Tantsura, "MPLS
Segment Routing in IP Networks", draft-bryant-mpls- Segment Routing in IP Networks", draft-bryant-mpls-
unified-ip-sr-03 (work in progress), October 2017. unified-ip-sr-03 (work in progress), October 2017.
[I-D.ietf-6man-segment-routing-header] [I-D.ietf-6man-segment-routing-header]
Filsfils, C., Previdi, S., Leddy, J., Matsushima, S., and Filsfils, C., Previdi, S., Leddy, J., Matsushima, S., and
d. daniel.voyer@bell.ca, "IPv6 Segment Routing Header d. daniel.voyer@bell.ca, "IPv6 Segment Routing Header
(SRH)", draft-ietf-6man-segment-routing-header-14 (work in (SRH)", draft-ietf-6man-segment-routing-header-17 (work in
progress), June 2018. progress), March 2019.
[I-D.ietf-idr-bgp-ls-segment-routing-ext] [I-D.ietf-idr-bgp-ls-segment-routing-ext]
Previdi, S., Talaulikar, K., Filsfils, C., Gredler, H., Previdi, S., Talaulikar, K., Filsfils, C., Gredler, H.,
and M. Chen, "BGP Link-State extensions for Segment and M. Chen, "BGP Link-State extensions for Segment
Routing", draft-ietf-idr-bgp-ls-segment-routing-ext-08 Routing", draft-ietf-idr-bgp-ls-segment-routing-ext-12
(work in progress), May 2018. (work in progress), March 2019.
[I-D.ietf-isis-segment-routing-extensions] [I-D.ietf-isis-segment-routing-extensions]
Previdi, S., Ginsberg, L., Filsfils, C., Bashandy, A., Previdi, S., Ginsberg, L., Filsfils, C., Bashandy, A.,
Gredler, H., Litkowski, S., Decraene, B., and J. Tantsura, Gredler, H., and B. Decraene, "IS-IS Extensions for
"IS-IS Extensions for Segment Routing", draft-ietf-isis- Segment Routing", draft-ietf-isis-segment-routing-
segment-routing-extensions-19 (work in progress), July extensions-23 (work in progress), March 2019.
2018.
[I-D.ietf-ospf-ospfv3-segment-routing-extensions] [I-D.ietf-ospf-ospfv3-segment-routing-extensions]
Psenak, P., Filsfils, C., Previdi, S., Gredler, H., Psenak, P. and S. Previdi, "OSPFv3 Extensions for Segment
Shakir, R., Henderickx, W., and J. Tantsura, "OSPFv3 Routing", draft-ietf-ospf-ospfv3-segment-routing-
Extensions for Segment Routing", draft-ietf-ospf-ospfv3- extensions-23 (work in progress), January 2019.
segment-routing-extensions-15 (work in progress), August
2018.
[I-D.ietf-ospf-segment-routing-extensions] [I-D.ietf-ospf-segment-routing-extensions]
Psenak, P., Previdi, S., Filsfils, C., Gredler, H., Psenak, P., Previdi, S., Filsfils, C., Gredler, H.,
Shakir, R., Henderickx, W., and J. Tantsura, "OSPF Shakir, R., Henderickx, W., and J. Tantsura, "OSPF
Extensions for Segment Routing", draft-ietf-ospf-segment- Extensions for Segment Routing", draft-ietf-ospf-segment-
routing-extensions-25 (work in progress), April 2018. routing-extensions-27 (work in progress), December 2018.
[I-D.ietf-spring-segment-routing-mpls] [I-D.ietf-spring-segment-routing-mpls]
Bashandy, A., Filsfils, C., Previdi, S., Decraene, B., Bashandy, A., Filsfils, C., Previdi, S., Decraene, B.,
Litkowski, S., and R. Shakir, "Segment Routing with MPLS Litkowski, S., and R. Shakir, "Segment Routing with MPLS
data plane", draft-ietf-spring-segment-routing-mpls-14 data plane", draft-ietf-spring-segment-routing-mpls-19
(work in progress), June 2018. (work in progress), March 2019.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
 End of changes. 10 change blocks. 
21 lines changed or deleted 18 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/