Re: [Pce] 答复: PCEP Enhanced Errors

Dhruv Dhody <dhruv.ietf@gmail.com> Fri, 07 June 2019 11:16 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 07574120086 for <pce@ietfa.amsl.com>; Fri, 7 Jun 2019 04:16:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 p8yuG1ghcDW1 for <pce@ietfa.amsl.com>; Fri, 7 Jun 2019 04:16:21 -0700 (PDT)
Received: from mail-it1-x131.google.com (mail-it1-x131.google.com [IPv6:2607:f8b0:4864:20::131]) (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 DCD1C1200A4 for <pce@ietf.org>; Fri, 7 Jun 2019 04:16:20 -0700 (PDT)
Received: by mail-it1-x131.google.com with SMTP id x22so2115178itl.2 for <pce@ietf.org>; Fri, 07 Jun 2019 04:16:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=y1lS9T1/9wJinbtsLBnj1Cas0U4oUCeqy6O9XqENz/U=; b=L+Kezs9BD7MSRyH70Sy1jc+791t2ziEK5+B6/CoQkoKX1u4c0eHGlyTdnLjkCy844l 8B/xksKV+sEnhqHeX95jRrDEGtJU+GPViyp+PvMaqpQqnKm95bB9axZewCOZINwW4DBz 5I4poJjs7QnpOzw17Pz+K5YvlBnLR/RKbxDNIlC6rjafpcLC7H8elRsBwfXdyAVnNSQc 63mLybDfjTq97/vnQZ9KJkkXG5yJXmSNDO6HOzZYx0x/pRCfvKpyR6m8MtKfjStvo6JW aqq75ag95pasumn8OolDTZ3ufQSyXCeE8B6BToJTDDd+voXHFXdP/gmRSN089d9OOgaj 0QVA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=y1lS9T1/9wJinbtsLBnj1Cas0U4oUCeqy6O9XqENz/U=; b=NNPGINI8o9ar+PoXS7kNmJYhKsjtxk0ZkLrGzVMwuW1xSUAOicOL+Z3K2n6nDFgzZH b/PceqdVxitubNaYAtkr04H6Gus7gg7Ze05HA78LzIOdEZy8J3oGwRM/X3tE3qnMCKTw JI7Y+93u6XmANBibTOiu8xAncBBvzYB1xIpftJHrxbO5WJNtA+6VghMSgl5YUmdmC2vz Wv16hWz43UIBjvqwxtArkxwG5sypMwlwYWMi8GvRQsYewofnyGGS7wr7x0vjtODfge/l FAkX++n7MEIPAogzVFwlhnX4ZLi3TwXc8wsMx3SB4HGsmmex7FKs5+by3f7Xh6DtR1az kJvw==
X-Gm-Message-State: APjAAAWBZkJB5EOL4aZdcnsONLXMGSog0Q3KKaT+56m2uV7g/lI/tyFA f10jgX9MLMerI63dhK/1Vt5N70Y1n0Y/dlQQr+g=
X-Google-Smtp-Source: APXvYqze5fkagEamZ3gbq9ZTL017wTYEjtOyfy9OAgXotdGfi6Sokhbq7afo+p8GnRz+jhzTMPynRpB2C81A9kLP2Mw=
X-Received: by 2002:a24:ce41:: with SMTP id v62mr3851259itg.96.1559906179949; Fri, 07 Jun 2019 04:16:19 -0700 (PDT)
MIME-Version: 1.0
References: <058701d517c5$15653c90$402fb5b0$@olddog.co.uk> <E0C26CAA2504C84093A49B2CAC3261A43B7E5084@dggeml511-mbx.china.huawei.com> <CAB75xn44qYLS_QHfE5=gUkdOY2Qka0tLGgx4asuVqe8kjH2keQ@mail.gmail.com> <E0C26CAA2504C84093A49B2CAC3261A43B7E713E@dggeml511-mbx.china.huawei.com>
In-Reply-To: <E0C26CAA2504C84093A49B2CAC3261A43B7E713E@dggeml511-mbx.china.huawei.com>
From: Dhruv Dhody <dhruv.ietf@gmail.com>
Date: Fri, 07 Jun 2019 16:45:43 +0530
Message-ID: <CAB75xn6nvekKQ0_E1vPnKhk-1xyxnDY+byTx0V5_QTmQA+hOqQ@mail.gmail.com>
To: "Zhenghaomian (Zhenghaomian, Optical Technology Research Dept)" <zhenghaomian@huawei.com>
Cc: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "pce@ietf.org" <pce@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/xST7hTkxjFBgBbiAtf0LNsVUqjE>
Subject: Re: [Pce] 答复: PCEP Enhanced Errors
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 07 Jun 2019 11:16:24 -0000

Hi Haomian, WG,

Note that, this guideline should be for any 'future' draft, since this update
would have to use [I-D.ietf-pce-enhanced-errors] as a normative reference (as
they will be providing details of Error-criticality and Propagation etc).
For any 'mature' draft it is better to use [I-D.ietf-pce-enhanced-errors]
as informative reference with details of error handling added into
[I-D.ietf-pce-enhanced-errors] itself (as already done for some drafts).

Thus my suggestion would be to say -

Error and Notification handling as per [I-D.ietf-pce-enhanced-errors] should
be considered in PCE documents that include multi-PCE interactions. A
requirement for the editors of these drafts is to evaluate the applicability
of the procedure in [I-D.ietf-pce-enhanced-errors] and provide details about
the "Error-criticality" TLV and "Propagation" TLV for errors and notifications
defined in the draft. Examples of this can be found in section 5.4.3 of
[I-D.ietf-pce-enhanced-errors].

Thoughts?

Thanks!
Dhruv

On Thu, Jun 6, 2019 at 3:38 PM Zhenghaomian (Zhenghaomian, Optical
Technology Research Dept) <zhenghaomian@huawei.com> wrote:
>
> Hi, Dhruv, WG,
>
> I think the following text would be helpful as the guideline.
>
> ------ guideline text starts ---------
> Error handling should be considered in any multi-PCE drafts. A requirement for the editors of these drafts is to evaluate what error types between PCE may occur in the specified scenarios in the draft and whether new error types need to be extended. It is also requested to check the applicability of the procedures specified in draft-ietf-pce-enhanced-errors to both the existing and the extending error types. For PCE protocol extension who gives new error types, it is requested to provide description on the applicability of "Propagation" TLV and "Error-criticality" TLV.
> ------ guideline text ends ---------
>
> Any comments or rephrasing would be more than welcome, thank you.
>
> Best wishes,
> Haomian
> -----邮件原件-----
> 发件人: Dhruv Dhody [mailto:dhruv.ietf@gmail.com]
> 发送时间: 2019年6月3日 13:28
> 收件人: Zhenghaomian (Zhenghaomian, Optical Technology Research Dept) <zhenghaomian@huawei.com>
> 抄送: adrian@olddog.co.uk; pce@ietf.org
> 主题: Re: [Pce] 答复: PCEP Enhanced Errors
>
> Hi Haomian,
>
> Lets come up with the guidelines (and get the agreement on the mailing
> list) first!
> Then, lets take one of the I-D as example and work with the authors to incorporate the guidelines.
>
> We can worry about how to add guidelines to the wiki later. We can also add the guidelines in your draft itself.
>
> Thanks!
> Dhruv
>
>
> On Mon, Jun 3, 2019 at 7:20 AM Zhenghaomian (Zhenghaomian, Optical Technology Research Dept) <zhenghaomian@huawei.com> wrote:
> >
> > Hi, Adrian, WGs,
> >
> > Thank you for bringing the issue to the list, I think we agreed the direction you mentioned 'no haste but keep moving' in Prague. We would definitely like to provide some text as guideline for other documents, either in the draft or on the wiki page, or both. Personally I need to understand the context in the wiki page before doing that. Do the chairs want to see a separate paragraph talking about the error handling? Or we put the text together with other sections like 'implement policy'?
> >
> > We can move on providing text once we can agree on how to manage, thank you.
> >
> > Best wishes,
> > Haomian (as one of the co-authors)
> >
> > -----邮件原件-----
> > 发件人: Pce [mailto:pce-bounces@ietf.org] 代表 Adrian Farrel
> > 发送时间: 2019年5月31日 23:25
> > 收件人: pce@ietf.org
> > 主题: [Pce] PCEP Enhanced Errors
> >
> > Hi,
> >
> > In Prague we had a discussion of draft-ietf-pce-enhanced-errors.
> >
> > My recollection is that we decided that there was no great hurry to push this document to completion, but that we didn't want to abandon it.
> >
> > Checking back with the minutes, there was an objective that we encourage authors of other documents to adhere to the error behaviours described in this document. We do this possibly by putting text on a wiki page, but first by discussing the guidelines on the mailing list. Looks like we were particularly interested in the behaviours when there are multiple PCEs present.
> >
> > We also discussed the possibilities for encouraging an "Error Handling"
> > section in all our drafts, or at least for a section on "Error Handling in Multi-PCE Scenarios" when applicable.
> >
> > Would the authors of draft-ietf-pce-enhanced-errors like to take the lead on this?
> >
> > Thanks,
> > Adrian
> >
> > _______________________________________________
> > Pce mailing list
> > Pce@ietf.org
> > https://www.ietf.org/mailman/listinfo/pce
> > _______________________________________________
> > Pce mailing list
> > Pce@ietf.org
> > https://www.ietf.org/mailman/listinfo/pce