draft-ietf-teas-network-assigned-upstream-label-05.txt   draft-ietf-teas-network-assigned-upstream-label-06.txt 
TEAS Working Group X. Zhang, Ed. TEAS Working Group X. Zhang, Ed.
Internet-Draft Huawei Technologies Internet-Draft Huawei Technologies
Intended status: Standards Track V. Beeram, Ed. Updates: 3473 (if approved) V. Beeram, Ed.
Expires: September 14, 2017 Juniper Networks Intended status: Standards Track Juniper Networks
I. Bryskin Expires: December 24, 2017 I. Bryskin
Huawei Technologies Huawei Technologies
D. Ceccarelli D. Ceccarelli
Ericsson Ericsson
O. Gonzalez de Dios O. Gonzalez de Dios
Telefonica Telefonica
March 13, 2017 June 22, 2017
Network Assigned Upstream-Label Network Assigned Upstream-Label
draft-ietf-teas-network-assigned-upstream-label-05 draft-ietf-teas-network-assigned-upstream-label-06
Abstract Abstract
This document discusses a Generalized Multi-Protocol Label Switching This document discusses a Generalized Multi-Protocol Label Switching
(GMPLS) Resource reSerVation Protocol with Traffic Engineering (RSVP- (GMPLS) Resource reSerVation Protocol with Traffic Engineering (RSVP-
TE) mechanism that enables the network to assign an upstream label TE) mechanism that enables the network to assign an upstream label
for a bidirectional LSP. This is useful in scenarios where a given for a bidirectional LSP. This is useful in scenarios where a given
node does not have sufficient information to assign the correct node does not have sufficient information to assign the correct
upstream label on its own and needs to rely on the downstream node to upstream label on its own and needs to rely on the downstream node to
pick an appropriate label. pick an appropriate label. This document updates RFC3473 as it
defines processing for a special label value.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
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 September 14, 2017. This Internet-Draft will expire on December 24, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 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
skipping to change at page 2, line 31 skipping to change at page 2, line 36
2.2. Backwards Compatibility . . . . . . . . . . . . . . . . . 4 2.2. Backwards Compatibility . . . . . . . . . . . . . . . . . 4
3. Use-Case: Wavelength Setup for IP over Optical Networks . . . 4 3. Use-Case: Wavelength Setup for IP over Optical Networks . . . 4
3.1. Initial Setup . . . . . . . . . . . . . . . . . . . . . . 5 3.1. Initial Setup . . . . . . . . . . . . . . . . . . . . . . 5
3.2. Wavelength Change . . . . . . . . . . . . . . . . . . . . 6 3.2. Wavelength Change . . . . . . . . . . . . . . . . . . . . 6
4. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6 4. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6
5. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 6 5. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 6
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
7. Security Considerations . . . . . . . . . . . . . . . . . . . 7 7. Security Considerations . . . . . . . . . . . . . . . . . . . 7
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 7
8.1. Normative References . . . . . . . . . . . . . . . . . . 7 8.1. Normative References . . . . . . . . . . . . . . . . . . 7
8.2. Informative References . . . . . . . . . . . . . . . . . 7 8.2. Informative References . . . . . . . . . . . . . . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8
1. Introduction 1. Introduction
The Generalized Multi-Protocol Label Switching (GMPLS) Resource The Generalized Multi-Protocol Label Switching (GMPLS) Resource
reSerVation Protocol with Traffic Engineering (RSVP-TE) extensions reSerVation Protocol with Traffic Engineering (RSVP-TE) extensions
for setting up a bidirectional LSP are specified in [RFC3473]. The for setting up a bidirectional LSP are specified in [RFC3473]. The
bidirectional LSP setup is indicated by the presence of an bidirectional LSP setup is indicated by the presence of an
UPSTREAM_LABEL Object in the PATH message. As per the existing setup UPSTREAM_LABEL Object in the PATH message. As per the existing setup
procedure outlined for a bidirectional LSP, each upstream node must procedure outlined for a bidirectional LSP, each upstream node must
 End of changes. 6 change blocks. 
8 lines changed or deleted 9 lines changed or added

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