draft-kumarkini-mpls-spring-lsp-ping-04.txt   draft-kumarkini-mpls-spring-lsp-ping-05.txt 
Network Work group N. Kumar Network Work group N. Kumar
Internet-Draft G. Swallow Internet-Draft G. Swallow
Intended status: Standards Track C. Pignataro Intended status: Standards Track C. Pignataro
Expires: January 31, 2016 Cisco Systems, Inc. Expires: August 3, 2016 Cisco Systems, Inc.
N. Akiya N. Akiya
Big Switch Networks Big Switch Networks
S. Kini S. Kini
Ericsson Individual
H. Gredler H. Gredler
Juniper Networks Juniper Networks
M. Chen M. Chen
Huawei Huawei
July 30, 2015 January 31, 2016
Label Switched Path (LSP) Ping/Trace for Segment Routing Networks Using Label Switched Path (LSP) Ping/Trace for Segment Routing Networks Using
MPLS Dataplane MPLS Dataplane
draft-kumarkini-mpls-spring-lsp-ping-04 draft-kumarkini-mpls-spring-lsp-ping-05
Abstract Abstract
Segment Routing architecture leverages the source routing and Segment Routing architecture leverages the source routing and
tunneling paradigms and can be directly applied to MPLS data plane. tunneling paradigms and can be directly applied to MPLS data plane.
A node steers a packet through a controlled set of instructions A node steers a packet through a controlled set of instructions
called segments, by prepending the packet with a Segment Routing called segments, by prepending the packet with a Segment Routing
header. header.
The segment assignment and forwarding semantic nature of Segment The segment assignment and forwarding semantic nature of Segment
skipping to change at page 2, line 4 skipping to change at page 2, line 4
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 http://datatracker.ietf.org/drafts/current/. Drafts is at http://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 January 31, 2016. This Internet-Draft will expire on August 3, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2016 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
(http://trustee.ietf.org/license-info) in effect on the date of (http://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 14, line 26 skipping to change at page 14, line 26
[I-D.filsfils-spring-segment-routing-use-cases] [I-D.filsfils-spring-segment-routing-use-cases]
Filsfils, C., Francois, P., Previdi, S., Decraene, B., Filsfils, C., Francois, P., Previdi, S., Decraene, B.,
Litkowski, S., Horneffer, M., Milojevic, I., Shakir, R., Litkowski, S., Horneffer, M., Milojevic, I., Shakir, R.,
Ytti, S., Henderickx, W., Tantsura, J., Kini, S., and E. Ytti, S., Henderickx, W., Tantsura, J., Kini, S., and E.
Crabbe, "Segment Routing Use Cases", draft-filsfils- Crabbe, "Segment Routing Use Cases", draft-filsfils-
spring-segment-routing-use-cases-01 (work in progress), spring-segment-routing-use-cases-01 (work in progress),
October 2014. October 2014.
[I-D.ietf-spring-segment-routing] [I-D.ietf-spring-segment-routing]
Filsfils, C., Previdi, S., Decraene, B., Litkowski, S., Filsfils, C., Previdi, S., Decraene, B., Litkowski, S.,
and R. Shakir, "Segment Routing Architecture", draft-ietf- and r. rjs@rob.sh, "Segment Routing Architecture", draft-
spring-segment-routing-03 (work in progress), May 2015. ietf-spring-segment-routing-07 (work in progress),
December 2015.
[RFC0792] Postel, J., "Internet Control Message Protocol", STD 5, [RFC0792] Postel, J., "Internet Control Message Protocol", STD 5,
RFC 792, DOI 10.17487/RFC0792, September 1981, RFC 792, DOI 10.17487/RFC0792, September 1981,
<http://www.rfc-editor.org/info/rfc792>. <http://www.rfc-editor.org/info/rfc792>.
[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,
<http://www.rfc-editor.org/info/rfc2119>. <http://www.rfc-editor.org/info/rfc2119>.
skipping to change at page 16, line 18 skipping to change at page 16, line 18
US US
Email: cpignata@cisco.com Email: cpignata@cisco.com
Nobo Akiya Nobo Akiya
Big Switch Networks Big Switch Networks
Email: nobo.akiya.dev@gmail.com Email: nobo.akiya.dev@gmail.com
Sriganesh Kini Sriganesh Kini
Ericsson Individual
Email: sriganesh.kini@ericsson.com Email: sriganeshkini@gmail.com
Hannes Gredler Hannes Gredler
Juniper Networks Juniper Networks
Email: hannes@juniper.net Email: hannes@juniper.net
Mach(Guoyi) Chen Mach(Guoyi) Chen
Huawei Huawei
Email: mach.chen@huawei.com Email: mach.chen@huawei.com
 End of changes. 9 change blocks. 
10 lines changed or deleted 11 lines changed or added

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