draft-ietf-teas-network-assigned-upstream-label-11.txt   draft-ietf-teas-network-assigned-upstream-label-12.txt 
TEAS Working Group X. Zhang, Ed. TEAS Working Group X. Zhang, Ed.
Internet-Draft Huawei Technologies Internet-Draft Huawei Technologies
Updates: 3471, 3473, 6205 (if approved) V. Beeram, Ed. Updates: 3471, 3473, 6205 (if approved) V. Beeram, Ed.
Intended status: Standards Track Juniper Networks Intended status: Standards Track Juniper Networks
Expires: July 3, 2018 I. Bryskin Expires: August 2, 2018 I. Bryskin
Huawei Technologies Huawei Technologies
D. Ceccarelli D. Ceccarelli
Ericsson Ericsson
O. Gonzalez de Dios O. Gonzalez de Dios
Telefonica Telefonica
December 30, 2017 January 29, 2018
Network Assigned Upstream-Label Network Assigned Upstream-Label
draft-ietf-teas-network-assigned-upstream-label-11 draft-ietf-teas-network-assigned-upstream-label-12
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 Label Switched Path (LSP). This is useful in for a bidirectional Label Switched Path (LSP). This is useful in
scenarios where a given node does not have sufficient information to scenarios where a given node does not have sufficient information to
assign the correct upstream label on its own and needs to rely on the assign the correct upstream label on its own and needs to rely on the
downstream node to pick an appropriate label. This document updates downstream node to pick an appropriate label. This document updates
skipping to change at page 2, line 7 skipping to change at page 2, line 7
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 July 3, 2018. This Internet-Draft will expire on August 2, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2018 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 4, line 25 skipping to change at page 4, line 25
selection, it MUST specify a list of valid labels via the LABEL_SET selection, it MUST specify a list of valid labels via the LABEL_SET
object as specified in [RFC3473]. object as specified in [RFC3473].
In response, the downstream node picks an appropriate symmetric label In response, the downstream node picks an appropriate symmetric label
and sends it via the LABEL object in the Resv message. The upstream and sends it via the LABEL object in the Resv message. The upstream
node would then start using this symmetric label for both directions node would then start using this symmetric label for both directions
of the LSP. If the downstream node cannot pick the symmetric label, of the LSP. If the downstream node cannot pick the symmetric label,
it MUST issue a PathErr message with a "Routing Problem/Unacceptable it MUST issue a PathErr message with a "Routing Problem/Unacceptable
Label Value" indication. If the upstream node that signals an Label Value" indication. If the upstream node that signals an
Unassigned Upstream Label receives a label with the "all-ones" Unassigned Upstream Label receives a label with the "all-ones"
pattern in the LABEL object of the Resv message, it MUST issue a pattern or any other unacceptable label in the LABEL object of the
ResvErr message with a "Routing Problem/Unacceptable Label" Resv message, it MUST issue a ResvErr message with a "Routing
indication. Problem/Unacceptable Label" indication.
The upstream node will continue to signal the Unassigned Upstream The upstream node will continue to signal the Unassigned Upstream
Label in the Path message even after it receives an appropriate Label in the Path message even after it receives an appropriate
symmetric label in the Resv message. This is done to make sure that symmetric label in the Resv message. This is done to make sure that
the downstream node would pick a different symmetric label if and the downstream node would pick a different symmetric label if and
when it needs to change the label at a later time. If the upstream when it needs to change the label at a later time. If the upstream
node receives an unacceptable changed label, then it MUST issue a node receives an unacceptable changed label, then it MUST issue a
ResvErr message with a "Routing Problem/Unacceptable Label" ResvErr message with a "Routing Problem/Unacceptable Label"
indication. indication.
 End of changes. 6 change blocks. 
8 lines changed or deleted 8 lines changed or added

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