Re: [Pce] 答复: Re: A question about RFC8281 PCE-initiated LSPs.
Dhruv Dhody <dhruv.ietf@gmail.com> Wed, 24 January 2018 16:00 UTC
Return-Path: <dhruv.ietf@gmail.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C85512DA4C; Wed, 24 Jan 2018 08:00:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q8MS_RSN5eYK; Wed, 24 Jan 2018 08:00:52 -0800 (PST)
Received: from mail-qt0-x241.google.com (mail-qt0-x241.google.com [IPv6:2607:f8b0:400d:c0d::241]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9453512DA4E; Wed, 24 Jan 2018 08:00:46 -0800 (PST)
Received: by mail-qt0-x241.google.com with SMTP id l20so11475527qtj.11; Wed, 24 Jan 2018 08:00:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=U0SkQI5+5uF+sbdE5ugqP6Cm5FLWbwEqOD69VR1sL6k=; b=uyaOu+uWUYFvxIfB2u6UhVk6mqYddUpGKVTGGy06C6RhCN/+qbe47nJeig9gTPRkUr oUlKHABDtcyDy1IdwiCcMTKSw6AOyam89D0xLPSLF3/xtrpUQNaOyh8p+aPjttoiRcKH Kcfzjrah7HMhLvtcz9N2ZBKMzmtj+JqaCMxQ3PkHjjBdvXPdlsEVKen/gXFVnfG83sN/ TsajvmPj5L5UwsjTSrybCO7wyYpXUhq8mXau9E0rR/mjvFsNao7MOnhYYXnkRTYBXsQW jh5NdNrr4kSmMu/EtTA6z8ftsuBtFr0EJicDdzztdv89nrZ7WjH59GQXgEMZdT3SGG8l nWHg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=U0SkQI5+5uF+sbdE5ugqP6Cm5FLWbwEqOD69VR1sL6k=; b=oj9B8ZgaA/Q4YcT2HK62+vHKKBxS/M8zIUP2zPnGW85T7dl99i0MFV/6REK+dL3NNq Tzf0rSrMx0I7ot5XK46AnvJhbGGkdo1e35RukO7uAZ/X3SYMcgTJBrtiEzPi8ZEYthkc ECKDk5ZVHi3uLbx0hccxslesYpX75tbt4IzchpFKUwOK30t5XwWNyXjPNhHiHlu/oYUy AVutI0jXTuIOrqCnRic1Dw3yPMdcdQODZCeEm8fWgf8jrJqowTvsMuWMRkjjLDC/LWaE gkDC3YBa4Oa4dc3MLlDaonfOSF5LkTjoJFL8xu9d/Z6txqGfdW7RgYKPBHLEsR1WOqY+ YhOA==
X-Gm-Message-State: AKwxytcbUPlogr+zm9EHrMF1RQjKpVXSYtZfhvzV0wmAMOpHpMEXH9Wx EgGoiX2AQh+hNUuLmwtFh0vNxtB6R++gbrQsqLs=
X-Google-Smtp-Source: AH8x224IliSd36wTFpjeKkvrZteioPnzCxTxoTeJIxH11RAZwXtiTnIy9bLXLFriqMzou62hWh+VV/1ralW0A6SVhLk=
X-Received: by 10.200.27.52 with SMTP id y49mr10897449qtj.161.1516809644210; Wed, 24 Jan 2018 08:00:44 -0800 (PST)
MIME-Version: 1.0
Sender: dhruvdhody@gmail.com
X-Google-Sender-Delegation: dhruvdhody@gmail.com
Received: by 10.140.17.36 with HTTP; Wed, 24 Jan 2018 08:00:43 -0800 (PST)
In-Reply-To: <062501d39529$0e5278c0$2af76a40$@olddog.co.uk>
References: <OF75E385DF.CBF7EC89-ON4825821E.0028622F-4825821E.0029DC4E@LocalDomain> <OFE79AAD15.7263C513-ON4825821F.00317D23-4825821F.00335AF3@zte.com.cn> <062501d39529$0e5278c0$2af76a40$@olddog.co.uk>
From: Dhruv Dhody <dhruv.ietf@gmail.com>
Date: Wed, 24 Jan 2018 21:30:43 +0530
X-Google-Sender-Auth: crYSFdud6MpsQZP2pyuhOJG_wbE
Message-ID: <CAB75xn41hXGWATp9kQOa6BnKv8nUd-Gru379ws1mpuXOE1wz8A@mail.gmail.com>
To: Farrel Adrian <adrian@olddog.co.uk>
Cc: xiong.quan@zte.com.cn, Dhruv Dhody <dhruv.dhody@huawei.com>, Robert Varga <robert.varga@pantheon.tech>, draft-barth-pce-association-bidir@ietf.org, hu.fangwei@relay.zte.com.cn, "Siva Sivabalan (msiva)" <msiva@cisco.com>, pce@ietf.org, Edward Crabbe <edward.crabbe@gmail.com>, draft-ietf-pce-pcep-stateful-pce-gmpls@ietf.org
Content-Type: multipart/alternative; boundary="94eb2c14203a09053d056387c40d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/BnhivUfi-Mn2BNa1iMgVwbh4d2I>
X-Mailman-Approved-At: Wed, 24 Jan 2018 08:14:12 -0800
Subject: Re: [Pce] 答复: Re: A question about RFC8281 PCE-initiated LSPs.
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Path Computation Element <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Jan 2018 16:00:56 -0000
Thanks Adrian! This makes sense! Hope the authors of GMPLS draft could take this up. Regards, Dhruv On Wed, Jan 24, 2018 at 9:06 PM, Adrian Farrel <adrian@olddog.co.uk> wrote: > So, I think Quan is asking how to use a PCInitiate message to cause the > creation of a "co-routed" bidirectional LSP that is achieved in the > signaling plane by a single Path/Resv exchange. > > > > That is *G*MPLS function, but an answer would still be useful. > > > > Now, on a PCReq you need the B-bit to tell the PCE to compute a > bidirectional path. But what you should be looking at is the PCRep message. > That is, how does the PCE indicate that a bidirectional path has been > returned? And the answer is two points: > > > > 1. Since the requester asked for a bidirectional path, and since a path > has been computed, the PCC has every right to assume that the path can be > used for a bidirectional LSP. > > > > 2. The RP Object is present on the PCRep and also contains thee B-flag. > > > > Now, note that the PCInitiate most closely follows the PCRep. That is, it > flows from PCE to PCC and indicates the path of the LSP to be set up. > > > > Now, the PCInitiate carries the SRP Object, not the RP Object (just like > PCUpd message). > > > > There is a flags field in the SRP Object, but the only bit defined is in > 8281 for LSP removal. > > > > So, to expand on Quan's question: how do we Update an LSP that was set up > with the B-flag in the RP object, and how do we create an bidirectional LSP > using PCInitiate message? > > > > It is fine if the answer is "This is GMPLS function that possibly should > not have been in 5440, and we need to look at some additional work for > GMPLS extensions for 8231 and 8281." > > > > draft-ietf-pce-pcep-stateful-pce-gmpls is a starting point and should, > perhaps, define a B flag for the SRP on the PCUpd that would then also be > available automatically on the PCInitiate. > > > > Yours ramblingly, > > Adrian > > > > > > > > > > *From:* Pce [mailto:pce-bounces@ietf.org] *On Behalf Of * > xiong.quan@zte.com.cn > *Sent:* 24 January 2018 09:21 > *To:* dhruv.dhody@huawei.com > *Cc:* robert.varga@pantheon.tech; draft-barth-pce-association- > bidir@ietf.org; hu.fangwei@relay.zte.com.cn; msiva@cisco.com; pce@ietf.org; > edward.crabbe@gmail.com > *Subject:* [Pce] 答复: Re: A question about RFC8281 PCE-initiated LSPs. > > > > Hi Dhruv, > > > I agree PCInitiate message including the ASSOCIATION Object may create a > new LSP. > > But it still need to create bi-directional LSP by two messages. > > In some scenario, like PTN, we need to establish a bi-directional LSP by > one message of a PCE request. > > In my opinion, this is the requirement to create a bi-directional LSP by a > PCInitiate message. > > > Thanks, > Quan > > > > -------------------------------------------------------------------------------- > > [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] > Re: [Pce] A question about RFC8281 PCE-initiated LSPs. > > -------------------------------------------------------------------------------- > > > To: "xiong.quan at zte.com.cn" <xiong.quan at zte.com.cn>, > "draft-barth-pce-association-bidir at ietf.org" > <draft-barth-pce-association-bidir at ietf.org> > Subject: Re: [Pce] A question about RFC8281 PCE-initiated LSPs. > From: Dhruv Dhody <dhruv.dhody at huawei.com> > Date: Tue, 23 Jan 2018 11:21:15 +0000 > Accept-language: en-GB, zh-CN, en-US > Archived-at: <https://mailarchive.ietf.org/arch/msg/pce/ > Vx2UV03boBu2HHvP4qWETgxHr90> > Cc: "edward.crabbe at gmail.com" <edward.crabbe at gmail.com>, "inaminei > at google.com" <inaminei at google.com>, "msiva at cisco.com" <msiva at > cisco.com>, "robert.varga at pantheon.tech" <robert.varga at > pantheon.tech>, "pce at ietf.org" <pce at ietf.org>, "hu.fangwei at > relay.zte.com.cn" <hu.fangwei at relay.zte.com.cn>, "julien.meuric at > orange.com" <julien.meuric at orange.com>, "jonathan.hardwick at > metaswitch.com" <jonathan.hardwick at metaswitch.com> > Delivered-to: pce at ietfa.amsl.com > In-reply-to: <OF75E385DF.CBF7EC89-ON4825821E.0028622F-4825821E. > 0029DC4E@zte.com.cn> > List-archive: <https://mailarchive.ietf.org/arch/browse/pce/> > List-help: <mailto:pce-request@ietf.org?subject=help > <pce-request@ietf.org?subject=help>> > List-id: Path Computation Element <pce.ietf.org> > List-post: <mailto:pce@ietf.org <pce@ietf.org>> > List-subscribe: <https://www.ietf.org/mailman/listinfo/pce>, < > mailto:pce-request@ietf.org?subject=subscribe > <pce-request@ietf.org?subject=subscribe>> > List-unsubscribe: <https://www.ietf.org/mailman/options/pce>, < > mailto:pce-request@ietf.org?subject=unsubscribe > <pce-request@ietf.org?subject=unsubscribe>> > References: <OF75E385DF.CBF7EC89-ON4825821E.0028622F-4825821E. > 0029DC4E@zte.com.cn> > Thread-index: AQHTlB0CgKqVuxcwbkmqwLTk/0dyLaOBTApQ > Thread-topic: [Pce] A question about RFC8281 PCE-initiated LSPs. > > -------------------------------------------------------------------------------- > > Hi Quan, > > > > As per [1]: > A PCE initiating a new LSP, can include the association group > information. This is done by including the ASSOCIATION Object in a > > PCInitiate message. > > > > So when a new LSP is created by PCE, you could still indicate the > association. The association is not limited to existing LSPs. > > > > Hope this helps! Let me know if I understood your question correctly! > > > > Regards, > > Dhruv > > > > [1] https://tools.ietf.org/html/draft-ietf-pce-association- > group-04#section-5.2.1 > > > > From: xiong.quan at zte.com.cn [mailto:xiong.quan <xiong.quan> at > zte.com.cn] > Sent: 23 January 2018 13:07 > To: Dhruv Dhody <dhruv.dhody at huawei.com>; draft-barth-pce-association-bidir > at ietf.org > Cc: edward.crabbe at gmail.com; inaminei at google.com; msiva at cisco.com; > robert.varga at pantheon.tech; pce at ietf.org; hu.fangwei at > relay.zte.com.cn; julien.meuric at orange.com; jonathan.hardwick at > metaswitch.com > Subject: Re: [Pce] A question about RFC8281 PCE-initiated LSPs. > > > > Hi Dhruv, > > > Thank you for the reply!O(∩_∩)O~ > > I agree two created PCE-initiated LSPs may be associated by ASSOCIATION > object as discussed in draft-barth-pce-association-bidir. > > But if there is no LSP existed, how to request a bi-directional TE LSP > from PCE in PCE initiated operation? > > > Quan Xiong > > -------------------------------------------------------------------------------- > > [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] > Re: [Pce] A question about RFC8281 PCE-initiated LSPs. > > -------------------------------------------------------------------------------- > > > To: "xiong.quan at zte.com.cn" <xiong.quan at zte.com.cn>, "edward.crabbe > at gmail.com" <edward.crabbe at gmail.com>, "inaminei at google.com" > <inaminei at google.com>, "msiva at cisco.com" <msiva at cisco.com>, > "robert.varga at pantheon.tech" <robert.varga at pantheon.tech> > Subject: Re: [Pce] A question about RFC8281 PCE-initiated LSPs. > From: Dhruv Dhody <dhruv.dhody at huawei.com> > Date: Tue, 23 Jan 2018 03:28:27 +0000 > Accept-language: en-GB, en-US > Archived-at: <https://mailarchive.ietf.org/arch/msg/pce/ > ryZRIHK4zGoqSAsxMFQetTWDjbY> > Cc: "hu.fangwei at relay.zte.com.cn" <hu.fangwei at relay.zte.com.cn>, > "pce at ietf.org" <pce at ietf.org>, "draft-barth-pce-association-bidir > at ietf.org" <draft-barth-pce-association-bidir at ietf.org> > Delivered-to: pce at ietfa.amsl.com > In-reply-to: <OF60BFF49D.2F7F81DC-ON48258217.0026FFA8-4825821E.000BA102 > at zte.com.cn> > List-archive: <https://mailarchive.ietf.org/arch/browse/pce/> > List-help: <mailto:pce-request <pce-request> at ietf.org?subject=help> > List-id: Path Computation Element <pce.ietf.org> > List-post: <mailto:pce <pce> at ietf.org> > List-subscribe: <https://www.ietf.org/mailman/listinfo/pce>, < > mailto:pce-request <pce-request> at ietf.org?subject=subscribe> > List-unsubscribe: <https://www.ietf.org/mailman/options/pce>, < > mailto:pce-request <pce-request> at ietf.org?subject=unsubscribe> > References: <OF60BFF49D.2F7F81DC-ON48258217.0026FFA8-4825821E.000BA102 at > zte.com.cn> > Thread-index: AQHTk+76gKqVuxcwbkmqwLTk/0dyLaOAy0lA > Thread-topic: [Pce] A question about RFC8281 PCE-initiated LSPs. > > -------------------------------------------------------------------------------- > > Hi Quan, > > > > Check out - https://datatracker.ietf.org/doc/draft-barth-pce- > association-bidir/ > > Authors are in cc, if you need to have further discussion! > > > > Thanks! > > Dhruv > > > > From: Pce [mailto:pce-bounces <pce-bounces> at ietf.org] On Behalf Of > xiong.quan at zte.com.cn > Sent: 23 January 2018 07:37 > To: edward.crabbe at gmail.com; inaminei at google.com; msiva at cisco.com; > robert.varga at pantheon.tech > Cc: hu.fangwei at relay.zte.com.cn; pce at ietf.org > Subject: [Pce] A question about RFC8281 PCE-initiated LSPs. > > > > Hi all, > > > I encountered a problem as following shown.O(∩_∩)O~ > > As defined in RFC5440,the PCC-initiated LSPs creation uses the B bit in RP > object of PCReq message to indicate the direction of the TE LSP. > When set, the PCC requests a bi-directional TE LSP and when cleared, the > TE LSP is unidirectional. > > And in stateful PCE, RFC8281 proposed the PCE-initiated LSPs and the PCE > could send a PCInitiate message to the PCC to request the creation of an > LSP. > The PCInitiate message carry the Objects including SRP, LSP ,END-POINTS > and ERO. But no B bit in SRP object. > > How to configure the direction of the TE LSP in PCE-initiated operation? > > Best Regards, > > Quan Xiong > > > > > > -------------------------------------------------------------------------------- > > > References: > [Pce] A question about RFC8281 PCE-initiated LSPs. > From: xiong . quan > Prev by Date: Re: [Pce] Adoption Poll for draft-raghu-pce-lsp-control-request > > Previous by thread: [Pce] A question about RFC8281 PCE-initiated LSPs. > Index(es): > Date > Thread > Note: Messages sent to this list are the opinions of the senders and do > not imply endorsement by the IETF. > > > -------------------------------------------------------------------------------- > > > References: > Re: [Pce] A question about RFC8281 PCE-initiated LSPs. > From: xiong . quan > Prev by Date: Re: [Pce] A question about RFC8281 PCE-initiated LSPs. > Next by Date: [Pce] iPOP 2018 First CFP > Previous by thread: Re: [Pce] A question about RFC8281 PCE-initiated LSPs. > Next by thread: [Pce] iPOP 2018 First CFP > Index(es): > Date > Thread > Note: Messages sent to this list are the opinions of the senders and do > not imply endorsement by the IETF. > > _______________________________________________ > Pce mailing list > Pce@ietf.org > https://www.ietf.org/mailman/listinfo/pce > >
- [Pce] 答复: Re: A question about RFC8281 PCE-initia… xiong.quan
- Re: [Pce] 答复: Re: A question about RFC8281 PCE-in… Adrian Farrel
- Re: [Pce] 答复: Re: A question about RFC8281 PCE-in… Dhruv Dhody