[Pce] Possible Errata regarding RFC6006
Udayasree palle <udayasree.palle@huawei.com> Fri, 13 December 2013 12:40 UTC
Return-Path: <udayasree.palle@huawei.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7EDEA1ADFC4 for <pce@ietfa.amsl.com>; Fri, 13 Dec 2013 04:40:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham
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 5Wnzh_tpzMOr for <pce@ietfa.amsl.com>; Fri, 13 Dec 2013 04:40:02 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id C957F1AE24B for <pce@ietf.org>; Fri, 13 Dec 2013 04:39:59 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BBJ18746; Fri, 13 Dec 2013 12:39:52 +0000 (GMT)
Received: from LHREML406-HUB.china.huawei.com (10.201.5.243) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 13 Dec 2013 12:39:35 +0000
Received: from SZXEML411-HUB.china.huawei.com (10.82.67.138) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 13 Dec 2013 12:39:49 +0000
Received: from szxeml561-mbx.china.huawei.com ([169.254.5.101]) by szxeml411-hub.china.huawei.com ([::1]) with mapi id 14.03.0158.001; Fri, 13 Dec 2013 20:39:45 +0800
From: Udayasree palle <udayasree.palle@huawei.com>
To: "draft-ietf-pce-pcep-p2mp-extensions@tools.ietf.org" <draft-ietf-pce-pcep-p2mp-extensions@tools.ietf.org>
Thread-Topic: Possible Errata regarding RFC6006
Thread-Index: AQHO+ABnc5dvcNPul0CCR9Xt0cYYsg==
Date: Fri, 13 Dec 2013 12:39:45 +0000
Message-ID: <EFF3DD5FFB75AC4D89158F068C24F4BB39DB2217@szxeml561-mbx.china.huawei.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.18.147.110]
Content-Type: multipart/alternative; boundary="_000_EFF3DD5FFB75AC4D89158F068C24F4BB39DB2217szxeml561mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "pce@ietf.org" <pce@ietf.org>, "jpv@cisco.com" <jpv@cisco.com>
Subject: [Pce] Possible Errata regarding RFC6006
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 13 Dec 2013 12:40:05 -0000
Hi All,
Please check and let me know your suggestion
Regards,
Udayasree
From: Udayasree palle
Sent: 10 December 2013 15:38
To: 'draft-ietf-pce-pcep-p2mp-extensions@tools.ietf.org'
Cc: julien.meuric@orange.com; jpv@cisco.com; adrian@olddog.co.uk; pce@ietf.org
Subject: Posasible Errata regarding draft-ietf-pce-pcep-p2mp-extensions
Hi All,
3.15. P2MP PCEP-ERROR Objects and Types
Error-Type=18; Error-Value=1: if a PCE has not received the last
piece of the fragmented message, it should send an error message to
the sender to signal that it has received an incomplete message
(i.e., "Fragmented request failure"). The PCE MUST send a PCErr
message with a PCEP-ERROR object (Error-Type=18) and an Error-Value
(Error-Value=1).
The fragmentation is done for both request and reply messages, but it looks like the error value is defined only for request.
Suggested Text:
Make it generic
- Remove the word 'request'
- Replace PCE with PCEP speaker
- Update IANA
Error-Type=18; Error-Value=1: if a PCEP speaker has not received the last
piece of the fragmented message, it should send an error message to
the sender to signal that it has received an incomplete message
(i.e., "Fragmented failure"). The PCEP speaker MUST send a PCErr
message with a PCEP-ERROR object (Error-Type=18) and an Error-Value
(Error-Value=1).
Or
Add a new Error-Value!
How to handle this?
Regards,
Udayasree
- [Pce] Possible Errata regarding RFC6006 Udayasree palle
- Re: [Pce] Possible Errata regarding RFC6006 Quintin zhao