[Pce] FW: I-D Action: draft-wu-pce-dns-pce-discovery-04.txt
Qin Wu <bill.wu@huawei.com> Sun, 26 January 2014 02:51 UTC
Return-Path: <bill.wu@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 BFEEB1A00DC for <pce@ietfa.amsl.com>; Sat, 25 Jan 2014 18:51:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.736
X-Spam-Level:
X-Spam-Status: No, score=-4.736 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.535, 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 ddgWe3cns897 for <pce@ietfa.amsl.com>; Sat, 25 Jan 2014 18:51:16 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id C033B1A00D6 for <pce@ietf.org>; Sat, 25 Jan 2014 18:51:15 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BCX67632; Sun, 26 Jan 2014 02:51:13 +0000 (GMT)
Received: from LHREML404-HUB.china.huawei.com (10.201.5.218) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.3.158.1; Sun, 26 Jan 2014 02:50:48 +0000
Received: from NKGEML404-HUB.china.huawei.com (10.98.56.35) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.3.158.1; Sun, 26 Jan 2014 02:51:11 +0000
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.56]) by nkgeml404-hub.china.huawei.com ([10.98.56.35]) with mapi id 14.03.0158.001; Sun, 26 Jan 2014 10:51:06 +0800
From: Qin Wu <bill.wu@huawei.com>
To: "pce@ietf.org" <pce@ietf.org>
Thread-Topic: I-D Action: draft-wu-pce-dns-pce-discovery-04.txt
Thread-Index: AQHPGj9DL7+heachiE+RjzZZhi7VjJqWShnw
Date: Sun, 26 Jan 2014 02:51:05 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABA43C762FE@nkgeml501-mbs.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.138.41.149]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: [Pce] FW: I-D Action: draft-wu-pce-dns-pce-discovery-04.txt
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: Sun, 26 Jan 2014 02:51:18 -0000
Hi, all: Here is the update to draft-wu-pce-dns-pce-discovery-04 based on review from DNS folks (Thanks for Yiyang for volunteer review)and Comments received in the last IETF meeting. The main changes are a.Use "pce+acronym" instead of "pce+apX" in the NAPTR service field format b.Take out TLS/TCP from Application Protocol Tags for now since TLS/TCP transport still needs more discussion. c. Remove txt record for PCE scope since capability query has already supported PCE scope discovery. Let us know if you think any other remaining issue that hasn't been addressed. Regards! -Qin -----Original Message----- From: I-D-Announce [mailto:i-d-announce-bounces@ietf.org] On Behalf Of internet-drafts@ietf.org Sent: Sunday, January 26, 2014 10:35 AM To: i-d-announce@ietf.org Subject: I-D Action: draft-wu-pce-dns-pce-discovery-04.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Path Computation Element (PCE) Discovery using Domain Name System(DNS) Authors : Qin Wu Dhruv Dhody Daniel King Diego R. Lopez Filename : draft-wu-pce-dns-pce-discovery-04.txt Pages : 23 Date : 2014-01-25 Abstract: Discovery of the Path Computation Element (PCE) within an IGP area or routing domain is possible using OSPF [RFC5088] and IS-IS [RFC5089]. However, it has been established that in certain deployment scenarios PCEs may not wish, or be able to participate within the IGP process. In those scenarios, it is beneficial for the Path Computation Client (PCC) (or other PCE) to discover PCEs via an alternative mechanism to those proposed in [RFC5088] and [RFC5089]. This document specifies the requirements, use cases, procedures and extensions to support PCE type and capability discovery via DNS. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-wu-pce-dns-pce-discovery/ There's also a htmlized version available at: http://tools.ietf.org/html/draft-wu-pce-dns-pce-discovery-04 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=draft-wu-pce-dns-pce-discovery-04 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ _______________________________________________ I-D-Announce mailing list I-D-Announce@ietf.org https://www.ietf.org/mailman/listinfo/i-d-announce Internet-Draft directories: http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt