From nobody Thu Sep 4 03:00:04 2014 Return-Path: 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 C2A331A0117 for ; Thu, 4 Sep 2014 03:00:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.132 X-Spam-Level: X-Spam-Status: No, score=0.132 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.668, 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 WjKyY_9WttBP for ; Thu, 4 Sep 2014 02:59:59 -0700 (PDT) Received: from smtptc.telefonica.com (smtptc.telefonica.com [195.76.34.108]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 263041A6EF3 for ; Thu, 4 Sep 2014 02:59:51 -0700 (PDT) Received: from smtptc.telefonica.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 7A9F13A01C5; Thu, 4 Sep 2014 11:59:49 +0200 (CEST) Received: from ESTGVMSP108.EUROPE.telefonica.corp (unknown [10.92.4.9]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtptc.telefonica.com (Postfix) with ESMTPS id 60B1F3A019A; Thu, 4 Sep 2014 11:59:49 +0200 (CEST) Received: from emea01-db3-obe.outbound.protection.outlook.com (10.92.5.139) by tls.telefonica.com (10.93.6.52) with Microsoft SMTP Server (TLS) id 14.3.146.2; Thu, 4 Sep 2014 11:59:48 +0200 Received: from AMSPR06MB104.eurprd06.prod.outlook.com (10.242.90.155) by AMSPR06MB104.eurprd06.prod.outlook.com (10.242.90.155) with Microsoft SMTP Server (TLS) id 15.0.1019.16; Thu, 4 Sep 2014 09:59:47 +0000 Received: from AMSPR06MB104.eurprd06.prod.outlook.com ([169.254.8.174]) by AMSPR06MB104.eurprd06.prod.outlook.com ([169.254.8.174]) with mapi id 15.00.1019.015; Thu, 4 Sep 2014 09:59:47 +0000 From: OSCAR GONZALEZ DE DIOS To: "draft-ietf-pce-inter-layer-ext@tools.ietf.org" Thread-Topic: Request for early allocation of code points for draft-ietf-pce-inter-layer-ext & status of draft Thread-Index: AQHPyCb1qESLDqSlbk6tqVot3iwRPQ== Date: Thu, 4 Sep 2014 09:59:47 +0000 Message-ID: Accept-Language: es-ES, en-US Content-Language: es-ES X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.3.9.131030 x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [195.235.92.26] x-microsoft-antispam: BCL:0;PCL:0;RULEID:;UriScan:; x-forefront-prvs: 0324C2C0E2 x-forefront-antispam-report: SFV:NSPM; SFS:(6009001)(199003)(51884002)(189002)(90102001)(76482001)(21056001)(101416001)(74662001)(83322001)(92566001)(77982001)(50986999)(54356999)(99396002)(46102001)(4396001)(92726001)(31966008)(16236675004)(2656002)(74502001)(86362001)(77096002)(83506001)(106356001)(87936001)(81342001)(85852003)(83072002)(64706001)(95666004)(20776003)(85306004)(105586002)(66066001)(79102001)(230783001)(110136001)(36756003)(229853001)(2351001)(107046002)(80022001)(106116001)(81542001); DIR:OUT; SFP:; SCL:1; SRVR:AMSPR06MB104; H:AMSPR06MB104.eurprd06.prod.outlook.com; FPR:; MLV:sfv; PTR:InfoNoRecords; A:1; MX:1; LANG:en; Content-Type: multipart/alternative; boundary="_000_D02E04B360B1Coscargonzalezdediostelefonicacom_" MIME-Version: 1.0 X-OriginatorOrg: telefonica.com X-TM-AS-MML: No Archived-At: http://mailarchive.ietf.org/arch/msg/pce/1tuH7Sp2lrDFGyoLBZVPcom-tWQ Cc: "pce@ietf.org" Subject: [Pce] Request for early allocation of code points for draft-ietf-pce-inter-layer-ext & status of draft X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Sep 2014 10:00:03 -0000 --_000_D02E04B360B1Coscargonzalezdediostelefonicacom_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Dear authors of draft-ietf-pce-inter-layer-ext, The draft draft-ietf-pce-inter-layer-ext, in its version 8 right now, intro= duces a set of new PCEP objects, which require object-class values. Current= recommended values clash with already allocated values. As suggested in the last IETF meeting in Toronto, the use of the early allo= cation procedure is recommended to handle the code points (when the draft i= s stable). Would it be possible that authors of the draft ask for early all= ocation of code points for draft-ietf-pce-inter-layer-ext ? On the other hand, I see that the draft has been stable for a while and eve= n has expired. Who is taking care of the updates of the draft? Is the draft= going to last call in the near future? Are you expecting a review? Best Regards, =D3scar ________________________________ Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, pu= ede contener informaci=F3n privilegiada o confidencial y es para uso exclus= ivo de la persona o entidad de destino. Si no es usted. el destinatario ind= icado, queda notificado de que la lectura, utilizaci=F3n, divulgaci=F3n y/o= copia sin autorizaci=F3n puede estar prohibida en virtud de la legislaci= =F3n vigente. Si ha recibido este mensaje por error, le rogamos que nos lo = comunique inmediatamente por esta misma v=EDa y proceda a su destrucci=F3n. The information contained in this transmission is privileged and confidenti= al information intended only for the use of the individual or entity named = above. If the reader of this message is not the intended recipient, you are= hereby notified that any dissemination, distribution or copying of this co= mmunication is strictly prohibited. If you have received this transmission = in error, do not read it. Please immediately reply to the sender that you h= ave received this communication in error and then delete it. Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat=E1rio= , pode conter informa=E7=E3o privilegiada ou confidencial e =E9 para uso ex= clusivo da pessoa ou entidade de destino. Se n=E3o =E9 vossa senhoria o des= tinat=E1rio indicado, fica notificado de que a leitura, utiliza=E7=E3o, div= ulga=E7=E3o e/ou c=F3pia sem autoriza=E7=E3o pode estar proibida em virtude= da legisla=E7=E3o vigente. Se recebeu esta mensagem por erro, rogamos-lhe = que nos o comunique imediatamente por esta mesma via e proceda a sua destru= i=E7=E3o --_000_D02E04B360B1Coscargonzalezdediostelefonicacom_ Content-Type: text/html; charset="iso-8859-1" Content-ID: <2F2817888AD7824FBD3A805AA5DF3127@eurprd06.prod.outlook.com> Content-Transfer-Encoding: quoted-printable
Dear authors of draft-ietf-pce-inter-layer-ext,

The dr= aft draft-ietf-pce-inter-layer-ext, in its version 8 right now, introduces = a set of new PCEP objects, which require object-class values. Current recom= mended values clash with already allocated values.

As sug= gested in the last IETF meeting in Toronto, the use of the early allocation= procedure is recommended to handle the code points (when the draft is stab= le). Would it be possible that authors of the draft ask for early allocation of code points for draft-ietf-p= ce-inter-layer-ext ?

On the= other hand, I see that the draft has been stable for a while and even has = expired. Who is taking care of the updates of the draft? Is the draft going= to last call in the near future? Are you expecting a review?

Best R= egards,

=D3sca= r 




Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, pu= ede contener informaci=F3n privilegiada o confidencial y es para uso exclus= ivo de la persona o entidad de destino. Si no es usted. el destinatario ind= icado, queda notificado de que la lectura, utilizaci=F3n, divulgaci=F3n y/o copia sin autorizaci=F3n puede e= star prohibida en virtud de la legislaci=F3n vigente. Si ha recibido este m= ensaje por error, le rogamos que nos lo comunique inmediatamente por esta m= isma v=EDa y proceda a su destrucci=F3n.

The information contained in this transmission is privileged and confidenti= al information intended only for the use of the individual or entity named = above. If the reader of this message is not the intended recipient, you are= hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If y= ou have received this transmission in error, do not read it. Please immedia= tely reply to the sender that you have received this communication in error= and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat=E1rio= , pode conter informa=E7=E3o privilegiada ou confidencial e =E9 para uso ex= clusivo da pessoa ou entidade de destino. Se n=E3o =E9 vossa senhoria o des= tinat=E1rio indicado, fica notificado de que a leitura, utiliza=E7=E3o, divulga=E7=E3o e/ou c=F3pia sem autoriza=E7=E3o p= ode estar proibida em virtude da legisla=E7=E3o vigente. Se recebeu esta me= nsagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mes= ma via e proceda a sua destrui=E7=E3o
 --_000_D02E04B360B1Coscargonzalezdediostelefonicacom_-- From nobody Thu Sep 4 23:00:09 2014 Return-Path: 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 EE2BD1A041C for ; Thu, 4 Sep 2014 23:00:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.969 X-Spam-Level: X-Spam-Status: No, score=-2.969 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.668, 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 frnGfaWCtVPR for ; Thu, 4 Sep 2014 23:00:01 -0700 (PDT) Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E79981A0414 for ; Thu, 4 Sep 2014 22:59:59 -0700 (PDT) Received: from 172.18.7.190 (EHLO lhreml403-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BJC06918; Fri, 05 Sep 2014 05:59:57 +0000 (GMT) Received: from SZXEMA408-HUB.china.huawei.com (10.82.72.40) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 5 Sep 2014 06:59:56 +0100 Received: from SZXEMA504-MBS.china.huawei.com ([169.254.8.159]) by SZXEMA408-HUB.china.huawei.com ([10.82.72.40]) with mapi id 14.03.0158.001; Fri, 5 Sep 2014 13:59:49 +0800 From: Fatai Zhang To: OSCAR GONZALEZ DE DIOS , "draft-ietf-pce-inter-layer-ext@tools.ietf.org" Thread-Topic: [Pce] Request for early allocation of code points for draft-ietf-pce-inter-layer-ext & status of draft Thread-Index: AQHPyCb1qESLDqSlbk6tqVot3iwRPZvx6Y/Q Date: Fri, 5 Sep 2014 05:59:49 +0000 Message-ID: References: In-Reply-To: Accept-Language: zh-CN, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.66.72.159] Content-Type: multipart/alternative; boundary="_000_F82A4B6D50F9464B8EBA55651F541CF85CB623BBSZXEMA504MBSchi_" MIME-Version: 1.0 X-CFilter-Loop: Reflected Archived-At: http://mailarchive.ietf.org/arch/msg/pce/En5WEYtDKapoSZx_JXiw3hTOdXc Cc: "pce@ietf.org" Subject: Re: [Pce] Request for early allocation of code points for draft-ietf-pce-inter-layer-ext & status of draft X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Sep 2014 06:00:06 -0000 --_000_F82A4B6D50F9464B8EBA55651F541CF85CB623BBSZXEMA504MBSchi_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi Oscar, I don't think we need to ask early allocation of code points, which is for = the special case (ie., early allocation is not the normal procedure) and th= e right values will be allocated during RFC publication stage (ie., the cla= sh will disappear) . The authors of this draft including me are taking care of this draft and we= always welcome any review comments from the WG. Note that the WG chairs told in the previous meeting that they would like t= o move forward [draft-ietf-pce-gmpls-pcep-extensions] first, and then move forward= this draft. Any further comments are apprecicated. Best Regards Fatai From: Pce [mailto:pce-bounces@ietf.org] On Behalf Of OSCAR GONZALEZ DE DIOS Sent: Thursday, September 04, 2014 6:00 PM To: draft-ietf-pce-inter-layer-ext@tools.ietf.org Cc: pce@ietf.org Subject: [Pce] Request for early allocation of code points for draft-ietf-p= ce-inter-layer-ext & status of draft Dear authors of draft-ietf-pce-inter-layer-ext, The draft draft-ietf-pce-inter-layer-ext, in its version 8 right now, intro= duces a set of new PCEP objects, which require object-class values. Current= recommended values clash with already allocated values. As suggested in the last IETF meeting in Toronto, the use of the early allo= cation procedure is recommended to handle the code points (when the draft i= s stable). Would it be possible that authors of the draft ask for early all= ocation of code points for draft-ietf-pce-inter-layer-ext ? On the other hand, I see that the draft has been stable for a while and eve= n has expired. Who is taking care of the updates of the draft? Is the draft= going to last call in the near future? Are you expecting a review? Best Regards, =D3scar ________________________________ Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, pu= ede contener informaci=F3n privilegiada o confidencial y es para uso exclus= ivo de la persona o entidad de destino. Si no es usted. el destinatario ind= icado, queda notificado de que la lectura, utilizaci=F3n, divulgaci=F3n y/o= copia sin autorizaci=F3n puede estar prohibida en virtud de la legislaci= =F3n vigente. Si ha recibido este mensaje por error, le rogamos que nos lo = comunique inmediatamente por esta misma v=EDa y proceda a su destrucci=F3n. The information contained in this transmission is privileged and confidenti= al information intended only for the use of the individual or entity named = above. If the reader of this message is not the intended recipient, you are= hereby notified that any dissemination, distribution or copying of this co= mmunication is strictly prohibited. If you have received this transmission = in error, do not read it. Please immediately reply to the sender that you h= ave received this communication in error and then delete it. Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat=E1rio= , pode conter informa=E7=E3o privilegiada ou confidencial e =E9 para uso ex= clusivo da pessoa ou entidade de destino. Se n=E3o =E9 vossa senhoria o des= tinat=E1rio indicado, fica notificado de que a leitura, utiliza=E7=E3o, div= ulga=E7=E3o e/ou c=F3pia sem autoriza=E7=E3o pode estar proibida em virtude= da legisla=E7=E3o vigente. Se recebeu esta mensagem por erro, rogamos-lhe = que nos o comunique imediatamente por esta mesma via e proceda a sua destru= i=E7=E3o --_000_F82A4B6D50F9464B8EBA55651F541CF85CB623BBSZXEMA504MBSchi_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Hi Oscar,<= o:p>

 = ;

I don̵= 7;t think we need to ask early allocation of code points, which is for the = special case (ie., early allocation is not the normal procedure) and the right values will be allocated during RFC publication stage (ie., = the clash will disappear) .

 = ;

The author= s of this draft including me are taking care of this draft and we always we= lcome any review comments from the WG.

 = ;

Note that = the WG chairs told in the previous meeting that they would like to move for= ward [draft-ietf= -pce-gmpls-pcep-extensions] first, and then move forward this draft.

 

Any further comments are ap= precicated.

 

 

Best Regards

 

Fatai

 = ;

From: Pce [mailto:pce-bounces@ietf.org] On Behalf Of OSCAR GONZALEZ DE DIOS
Sent: Thursday, September 04, 2014 6:00 PM
To: draft-ietf-pce-inter-layer-ext@tools.ietf.org
Cc: pce@ietf.org
Subject: [Pce] Request for early allocation of code points for draft= -ietf-pce-inter-layer-ext & status of draft

 

Dear authors = of draft-ietf-pce-inter-layer-ext,

 

The draft dra= ft-ietf-pce-inter-layer-ext, in its version 8 right now, introduces a set o= f new PCEP objects, which require object-class values. Current recommended values clash with already allocated values.<= /p>

 

As suggested = in the last IETF meeting in Toronto, the use of the early allocation proced= ure is recommended to handle the code points (when the draft is stable). Would it be possible that authors of the draft ask for ea= rly allocation of code points for draft-ietf-pce-inter-layer-ext ?

 

On the other = hand, I see that the draft has been stable for a while and even has expired= . Who is taking care of the updates of the draft? Is the draft going to last call in the near future? Are you expecting a review?

 

Best Regards,=

 

=D3scar =

 

 

 


Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, pu= ede contener informaci=F3n privilegiada o confidencial y es para uso exclus= ivo de la persona o entidad de destino. Si no es usted. el destinatario ind= icado, queda notificado de que la lectura, utilizaci=F3n, divulgaci=F3n y/o copia sin autorizaci=F3n puede e= star prohibida en virtud de la legislaci=F3n vigente. Si ha recibido este m= ensaje por error, le rogamos que nos lo comunique inmediatamente por esta m= isma v=EDa y proceda a su destrucci=F3n.

The information contained in this transmission is privileged and confidenti= al information intended only for the use of the individual or entity named = above. If the reader of this message is not the intended recipient, you are= hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If y= ou have received this transmission in error, do not read it. Please immedia= tely reply to the sender that you have received this communication in error= and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat=E1rio= , pode conter informa=E7=E3o privilegiada ou confidencial e =E9 para uso ex= clusivo da pessoa ou entidade de destino. Se n=E3o =E9 vossa senhoria o des= tinat=E1rio indicado, fica notificado de que a leitura, utiliza=E7=E3o, divulga=E7=E3o e/ou c=F3pia sem autoriza=E7=E3o p= ode estar proibida em virtude da legisla=E7=E3o vigente. Se recebeu esta me= nsagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mes= ma via e proceda a sua destrui=E7=E3o

--_000_F82A4B6D50F9464B8EBA55651F541CF85CB623BBSZXEMA504MBSchi_-- From nobody Fri Sep 5 04:50:25 2014 Return-Path: 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 E43E01A06DD for ; Fri, 5 Sep 2014 04:50:21 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.568 X-Spam-Level: X-Spam-Status: No, score=-2.568 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.668, 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 IMALs2HqTsyl for ; Fri, 5 Sep 2014 04:50:17 -0700 (PDT) Received: from smtpjc.telefonica.com (smtpjc.telefonica.com [81.47.204.76]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 562DE1A06D6 for ; Fri, 5 Sep 2014 04:50:15 -0700 (PDT) Received: from smtpjc.telefonica.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 0B0C92D01D5; Fri, 5 Sep 2014 13:50:13 +0200 (CEST) Received: from ESTGVMSP114.EUROPE.telefonica.corp (unknown [10.92.4.9]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtpjc.telefonica.com (Postfix) with ESMTPS id EF3E62D0152; Fri, 5 Sep 2014 13:50:12 +0200 (CEST) Received: from emea01-am1-obe.outbound.protection.outlook.com (10.92.5.139) by tls.telefonica.com (10.93.6.55) with Microsoft SMTP Server (TLS) id 14.3.146.2; Fri, 5 Sep 2014 13:50:12 +0200 Received: from AMSPR06MB102.eurprd06.prod.outlook.com (10.242.90.147) by AMSPR06MB485.eurprd06.prod.outlook.com (10.242.107.12) with Microsoft SMTP Server (TLS) id 15.0.1019.16; Fri, 5 Sep 2014 11:50:11 +0000 Received: from AMSPR06MB104.eurprd06.prod.outlook.com (10.242.90.155) by AMSPR06MB102.eurprd06.prod.outlook.com (10.242.90.147) with Microsoft SMTP Server (TLS) id 15.0.1019.16; Fri, 5 Sep 2014 11:50:10 +0000 Received: from AMSPR06MB104.eurprd06.prod.outlook.com ([169.254.8.174]) by AMSPR06MB104.eurprd06.prod.outlook.com ([169.254.8.174]) with mapi id 15.00.1019.015; Fri, 5 Sep 2014 11:50:10 +0000 From: OSCAR GONZALEZ DE DIOS To: Fatai Zhang , "draft-ietf-pce-inter-layer-ext@tools.ietf.org" Thread-Topic: [Pce] Request for early allocation of code points for draft-ietf-pce-inter-layer-ext & status of draft Thread-Index: AQHPyM6nAMGlV8VNbU25ji56a2IqQZvyjv4A Date: Fri, 5 Sep 2014 11:50:09 +0000 Message-ID: References: In-Reply-To: Accept-Language: es-ES, en-US Content-Language: es-ES X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.3.9.131030 x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [195.235.92.26] x-microsoft-antispam: BCL:0;PCL:0;RULEID:;UriScan:;UriScan:; x-forefront-prvs: 0325F6C77B x-forefront-antispam-report: SFV:NSPM; SFS:(10019016)(189002)(40134004)(51884002)(377454003)(199003)(79102001)(230783001)(76482001)(77982001)(4396001)(19580395003)(16236675004)(83322001)(19580405001)(19625215002)(90102001)(2656002)(101416001)(15202345003)(81342001)(46102001)(85306004)(54356999)(36756003)(76176999)(99396002)(86362001)(50986999)(18717965001)(92726001)(92566001)(21056001)(64706001)(77096002)(83072002)(85852003)(81542001)(87936001)(66066001)(74502001)(80022001)(107046002)(83506001)(74662001)(19617315012)(31966008)(19300405004)(20776003)(15975445006)(106116001)(106356001)(95666004)(105586002); DIR:OUT; SFP:1102; SCL:1; SRVR:AMSPR06MB102; H:AMSPR06MB104.eurprd06.prod.outlook.com; FPR:; MLV:sfv; PTR:InfoNoRecords; MX:1; A:1; LANG:en; Content-Type: multipart/alternative; boundary="_000_D02F266861074oscargonzalezdediostelefonicacom_" MIME-Version: 1.0 X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:; X-OriginatorOrg: telefonica.com X-TM-AS-MML: No Archived-At: http://mailarchive.ietf.org/arch/msg/pce/S2mVeOjsnyq04arG-oyJXRBxZmo Cc: "pce@ietf.org" Subject: Re: [Pce] Request for early allocation of code points for draft-ietf-pce-inter-layer-ext & status of draft X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Sep 2014 11:50:22 -0000 --_000_D02F266861074oscargonzalezdediostelefonicacom_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi Fatai, It is crystal clear that when the document becomes an RFC, IANA will assign= the correct number. In my humble opinion, requesting for the early allocation is not "a special= case", but the normal procedure that should be followed (obviously, it is = not the traditional way to do things), approved by IANA, so early implement= ations of stable documents have a code point that has no clashes. Furthermo= re, early allocated code points are maintained in the IANA registry. Tradit= ional way of adding the "suggested value" in the IANA section in the draft = has led to many problems. We even have a very recent case where a value use= d in a draft with early implementations has forced a value in an RFC with l= ess implementations to change. Summing up, I see absolutely no reason not to ask for the early allocat= ion, in this particular draft, and in all stable drafts in the working grou= p. I the particular case of this drafts, the suggested values of the new ob= jects are the same ones are values used in existing RFCs, complicating the = interoperability. In any case, requesting the early allocation is a decision to be taken by t= he authors of the draft. However, I would like to know also the opinions of= the chairs on wether the early allocation procedure is the "normal procedu= re" or the "special case" for stable working group documents. Best Regards, =D3scar De: Fatai Zhang > Fecha: viernes, 5 de septiembre de 2014 07:59 Para: Oscar Gonzalez de Dios >, "draft-ietf-pce-inter-layer-ext@tools.= ietf.org" > CC: "pce@ietf.org" > Asunto: RE: [Pce] Request for early allocation of code points for draft-iet= f-pce-inter-layer-ext & status of draft Hi Oscar, I don't think we need to ask early allocation of code points, which is for = the special case (ie., early allocation is not the normal procedure) and th= e right values will be allocated during RFC publication stage (ie., the cla= sh will disappear) . The authors of this draft including me are taking care of this draft and we= always welcome any review comments from the WG. Note that the WG chairs told in the previous meeting that they would like t= o move forward [draft-ietf-pce-gmpls-pcep-extensions] first, and then move forward= this draft. Any further comments are apprecicated. Best Regards Fatai From: Pce [mailto:pce-bounces@ietf.org] On Behalf Of OSCAR GONZALEZ DE DIOS Sent: Thursday, September 04, 2014 6:00 PM To: draft-ietf-pce-inter-layer-ext@tools.ietf.org Cc: pce@ietf.org Subject: [Pce] Request for early allocation of code points for draft-ietf-p= ce-inter-layer-ext & status of draft Dear authors of draft-ietf-pce-inter-layer-ext, The draft draft-ietf-pce-inter-layer-ext, in its version 8 right now, intro= duces a set of new PCEP objects, which require object-class values. Current= recommended values clash with already allocated values. As suggested in the last IETF meeting in Toronto, the use of the early allo= cation procedure is recommended to handle the code points (when the draft i= s stable). Would it be possible that authors of the draft ask for early all= ocation of code points for draft-ietf-pce-inter-layer-ext ? On the other hand, I see that the draft has been stable for a while and eve= n has expired. Who is taking care of the updates of the draft? Is the draft= going to last call in the near future? Are you expecting a review? Best Regards, =D3scar ________________________________ Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, pu= ede contener informaci=F3n privilegiada o confidencial y es para uso exclus= ivo de la persona o entidad de destino. Si no es usted. el destinatario ind= icado, queda notificado de que la lectura, utilizaci=F3n, divulgaci=F3n y/o= copia sin autorizaci=F3n puede estar prohibida en virtud de la legislaci= =F3n vigente. Si ha recibido este mensaje por error, le rogamos que nos lo = comunique inmediatamente por esta misma v=EDa y proceda a su destrucci=F3n. The information contained in this transmission is privileged and confidenti= al information intended only for the use of the individual or entity named = above. If the reader of this message is not the intended recipient, you are= hereby notified that any dissemination, distribution or copying of this co= mmunication is strictly prohibited. If you have received this transmission = in error, do not read it. Please immediately reply to the sender that you h= ave received this communication in error and then delete it. Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat=E1rio= , pode conter informa=E7=E3o privilegiada ou confidencial e =E9 para uso ex= clusivo da pessoa ou entidade de destino. Se n=E3o =E9 vossa senhoria o des= tinat=E1rio indicado, fica notificado de que a leitura, utiliza=E7=E3o, div= ulga=E7=E3o e/ou c=F3pia sem autoriza=E7=E3o pode estar proibida em virtude= da legisla=E7=E3o vigente. Se recebeu esta mensagem por erro, rogamos-lhe = que nos o comunique imediatamente por esta mesma via e proceda a sua destru= i=E7=E3o ________________________________ Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, pu= ede contener informaci=F3n privilegiada o confidencial y es para uso exclus= ivo de la persona o entidad de destino. Si no es usted. el destinatario ind= icado, queda notificado de que la lectura, utilizaci=F3n, divulgaci=F3n y/o= copia sin autorizaci=F3n puede estar prohibida en virtud de la legislaci= =F3n vigente. Si ha recibido este mensaje por error, le rogamos que nos lo = comunique inmediatamente por esta misma v=EDa y proceda a su destrucci=F3n. The information contained in this transmission is privileged and confidenti= al information intended only for the use of the individual or entity named = above. If the reader of this message is not the intended recipient, you are= hereby notified that any dissemination, distribution or copying of this co= mmunication is strictly prohibited. If you have received this transmission = in error, do not read it. Please immediately reply to the sender that you h= ave received this communication in error and then delete it. Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat=E1rio= , pode conter informa=E7=E3o privilegiada ou confidencial e =E9 para uso ex= clusivo da pessoa ou entidade de destino. Se n=E3o =E9 vossa senhoria o des= tinat=E1rio indicado, fica notificado de que a leitura, utiliza=E7=E3o, div= ulga=E7=E3o e/ou c=F3pia sem autoriza=E7=E3o pode estar proibida em virtude= da legisla=E7=E3o vigente. Se recebeu esta mensagem por erro, rogamos-lhe = que nos o comunique imediatamente por esta mesma via e proceda a sua destru= i=E7=E3o --_000_D02F266861074oscargonzalezdediostelefonicacom_ Content-Type: text/html; charset="iso-8859-1" Content-ID: Content-Transfer-Encoding: quoted-printable
Hi Fatai,

It is = crystal clear that when the document becomes an RFC, IANA will assign the c= orrect number.

In my = humble opinion, requesting for the early allocation is not “a special= case”, but the normal procedure that should be followed (obviously, = it is not the traditional way to do things), approved by IANA, so early implementations of stable documents have a code point th= at has no clashes. Furthermore, early allocated code points are maintained = in the IANA registry. Traditional way of adding the “suggested value&= #8221; in the IANA section in the draft has led to many problems. We even have a very recent case where a value used i= n a draft with early implementations has forced a value in an RFC with less= implementations to change. 

    Summing up, I see absolutely no reason not to ask for th= e early allocation, in this particular draft, and in all stable drafts in t= he working group. I the particular case of this drafts, the suggested value= s of the new objects are the same ones are values used in existing RFCs, complicating the interoperability. 

In any= case, requesting the early allocation is a decision to be taken by the aut= hors of the draft. However, I would like to know also the opinions of the c= hairs on wether the early allocation procedure is the “normal procedure” or the “special case= ” for stable working group documents.

Best R= egards,

=D3sca= r

     

De: Fatai Zhang <zhangfatai@huawei.com>
Fecha: viernes, 5 de septiembre de = 2014 07:59
Para: Oscar Gonzalez de Dios <oscar.gonzalezdedios@t= elefonica.com>, "draft-ietf-pce-inter-layer-ext@tools.ietf.org" <draft= -ietf-pce-inter-layer-ext@tools.ietf.org>
CC: "pce@ietf.org" <pce@ietf.= org>
Asunto: RE: [Pce] Request for early= allocation of code points for draft-ietf-pce-inter-layer-ext & status = of draft

Hi Oscar,

 

I don’t think we ne= ed to ask early allocation of code points, which is for the special case (i= e., early allocation is not the normal procedure) and the right values will be allocated during RFC publication stage (ie., = the clash will disappear) .

 

The authors of this draft= including me are taking care of this draft and we always welcome any revie= w comments from the WG.

 

Note that the WG chairs t= old in the previous meeting that they would like to move forward [draft-ietf-pce-gmpls-pcep= -extensions] first, and then move forward this draft.

 

Any further comments are apprecicated.

 

 

Best Regards

 

Fatai

 

From: Pce [mailto:pce-bounces@ietf.org] On Behalf Of OSCAR GONZALEZ DE DIOS
Sent: Thursday, September 04, 2014 6:00 PM
To: draft-ietf-pce-inter-layer-ext@tools.ietf.org
Cc: pce@ietf.org
Subject: [Pce] Request for early allocation of code points for draft= -ietf-pce-inter-layer-ext & status of draft

 

Dear authors of draft-ietf-pce-inter-= layer-ext,

 

The draft draft-ietf-pce-inter-layer-= ext, in its version 8 right now, introduces a set of new PCEP objects, whic= h require object-class values. Current recommended values clash with already allocated values.

 

As suggested in the last IETF meeting= in Toronto, the use of the early allocation procedure is recommended to ha= ndle the code points (when the draft is stable). Would it be possible that authors of the draft ask for early= allocation of code points for draft-ietf-pce-inter-layer-ext ?

 

On the other hand, I see that the dra= ft has been stable for a while and even has expired. Who is taking care of = the updates of the draft? Is the draft going to last call in the near future? Are you expecting a review?<= /p>

 

Best Regards,

 

=D3scar 

 

 

 


Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, pu= ede contener informaci=F3n privilegiada o confidencial y es para uso exclus= ivo de la persona o entidad de destino. Si no es usted. el destinatario ind= icado, queda notificado de que la lectura, utilizaci=F3n, divulgaci=F3n y/o copia sin autorizaci=F3n puede e= star prohibida en virtud de la legislaci=F3n vigente. Si ha recibido este m= ensaje por error, le rogamos que nos lo comunique inmediatamente por esta m= isma v=EDa y proceda a su destrucci=F3n.

The information contained in this transmission is privileged and confidenti= al information intended only for the use of the individual or entity named = above. If the reader of this message is not the intended recipient, you are= hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If y= ou have received this transmission in error, do not read it. Please immedia= tely reply to the sender that you have received this communication in error= and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat=E1rio= , pode conter informa=E7=E3o privilegiada ou confidencial e =E9 para uso ex= clusivo da pessoa ou entidade de destino. Se n=E3o =E9 vossa senhoria o des= tinat=E1rio indicado, fica notificado de que a leitura, utiliza=E7=E3o, divulga=E7=E3o e/ou c=F3pia sem autoriza=E7=E3o p= ode estar proibida em virtude da legisla=E7=E3o vigente. Se recebeu esta me= nsagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mes= ma via e proceda a sua destrui=E7=E3o



Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, pu= ede contener informaci=F3n privilegiada o confidencial y es para uso exclus= ivo de la persona o entidad de destino. Si no es usted. el destinatario ind= icado, queda notificado de que la lectura, utilizaci=F3n, divulgaci=F3n y/o copia sin autorizaci=F3n puede e= star prohibida en virtud de la legislaci=F3n vigente. Si ha recibido este m= ensaje por error, le rogamos que nos lo comunique inmediatamente por esta m= isma v=EDa y proceda a su destrucci=F3n.

The information contained in this transmission is privileged and confidenti= al information intended only for the use of the individual or entity named = above. If the reader of this message is not the intended recipient, you are= hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If y= ou have received this transmission in error, do not read it. Please immedia= tely reply to the sender that you have received this communication in error= and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat=E1rio= , pode conter informa=E7=E3o privilegiada ou confidencial e =E9 para uso ex= clusivo da pessoa ou entidade de destino. Se n=E3o =E9 vossa senhoria o des= tinat=E1rio indicado, fica notificado de que a leitura, utiliza=E7=E3o, divulga=E7=E3o e/ou c=F3pia sem autoriza=E7=E3o p= ode estar proibida em virtude da legisla=E7=E3o vigente. Se recebeu esta me= nsagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mes= ma via e proceda a sua destrui=E7=E3o
 --_000_D02F266861074oscargonzalezdediostelefonicacom_-- From nobody Fri Sep 5 08:56:11 2014 Return-Path: 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 AE88F1A0787 for ; Fri, 5 Sep 2014 08:56:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.866 X-Spam-Level: X-Spam-Status: No, score=-4.866 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.668, 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 Fj56Hpal6Stj for ; Fri, 5 Sep 2014 08:56:03 -0700 (PDT) Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E53641A0745 for ; Fri, 5 Sep 2014 08:55:46 -0700 (PDT) Received: from 172.18.7.190 (EHLO lhreml401-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BJC61919; Fri, 05 Sep 2014 15:55:45 +0000 (GMT) Received: from DFWEML702-CHM.china.huawei.com (10.193.5.72) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 5 Sep 2014 16:55:25 +0100 Received: from DFWEML706-CHM.china.huawei.com ([10.193.5.225]) by dfweml702-chm ([10.193.5.72]) with mapi id 14.03.0158.001; Fri, 5 Sep 2014 08:55:16 -0700 From: Leeyoung To: OSCAR GONZALEZ DE DIOS , Fatai Zhang , "draft-ietf-pce-inter-layer-ext@tools.ietf.org" Thread-Topic: [Pce] Request for early allocation of code points for draft-ietf-pce-inter-layer-ext & status of draft Thread-Index: AQHPyCb1qESLDqSlbk6tqVot3iwRPZvx6Y/QgAD6kYD//80ygA== Date: Fri, 5 Sep 2014 15:55:14 +0000 Message-ID: <7AEB3D6833318045B4AE71C2C87E8E1729C2D9C6@dfweml706-chm> References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.192.11.195] Content-Type: multipart/alternative; boundary="_000_7AEB3D6833318045B4AE71C2C87E8E1729C2D9C6dfweml706chm_" MIME-Version: 1.0 X-CFilter-Loop: Reflected Archived-At: http://mailarchive.ietf.org/arch/msg/pce/5ETyPQANc7noajpbyy3goSJARYk Cc: "pce@ietf.org" Subject: Re: [Pce] Request for early allocation of code points for draft-ietf-pce-inter-layer-ext & status of draft X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Sep 2014 15:56:08 -0000 --_000_7AEB3D6833318045B4AE71C2C87E8E1729C2D9C6dfweml706chm_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi Oscar and Fatai, I think the special case would be determined if the drafts have implementat= ions that have been shipped/deployed in production networks (which is above= lab trials) prior to the standardization. So any notes to the WG with implementations in production networks will jus= tify the early IANA allocation. Regards, Young From: Pce [mailto:pce-bounces@ietf.org] On Behalf Of OSCAR GONZALEZ DE DIOS Sent: Friday, September 05, 2014 6:50 AM To: Fatai Zhang; draft-ietf-pce-inter-layer-ext@tools.ietf.org Cc: pce@ietf.org Subject: Re: [Pce] Request for early allocation of code points for draft-ie= tf-pce-inter-layer-ext & status of draft Hi Fatai, It is crystal clear that when the document becomes an RFC, IANA will assign= the correct number. In my humble opinion, requesting for the early allocation is not "a special= case", but the normal procedure that should be followed (obviously, it is = not the traditional way to do things), approved by IANA, so early implement= ations of stable documents have a code point that has no clashes. Furthermo= re, early allocated code points are maintained in the IANA registry. Tradit= ional way of adding the "suggested value" in the IANA section in the draft = has led to many problems. We even have a very recent case where a value use= d in a draft with early implementations has forced a value in an RFC with l= ess implementations to change. Summing up, I see absolutely no reason not to ask for the early allocat= ion, in this particular draft, and in all stable drafts in the working grou= p. I the particular case of this drafts, the suggested values of the new ob= jects are the same ones are values used in existing RFCs, complicating the = interoperability. In any case, requesting the early allocation is a decision to be taken by t= he authors of the draft. However, I would like to know also the opinions of= the chairs on wether the early allocation procedure is the "normal procedu= re" or the "special case" for stable working group documents. Best Regards, =D3scar De: Fatai Zhang > Fecha: viernes, 5 de septiembre de 2014 07:59 Para: Oscar Gonzalez de Dios >, "draft-ietf-pce-inter-layer-ext@tools.= ietf.org" > CC: "pce@ietf.org" > Asunto: RE: [Pce] Request for early allocation of code points for draft-iet= f-pce-inter-layer-ext & status of draft Hi Oscar, I don't think we need to ask early allocation of code points, which is for = the special case (ie., early allocation is not the normal procedure) and th= e right values will be allocated during RFC publication stage (ie., the cla= sh will disappear) . The authors of this draft including me are taking care of this draft and we= always welcome any review comments from the WG. Note that the WG chairs told in the previous meeting that they would like t= o move forward [draft-ietf-pce-gmpls-pcep-extensions] first, and then move forward= this draft. Any further comments are apprecicated. Best Regards Fatai From: Pce [mailto:pce-bounces@ietf.org] On Behalf Of OSCAR GONZALEZ DE DIOS Sent: Thursday, September 04, 2014 6:00 PM To: draft-ietf-pce-inter-layer-ext@tools.ietf.org Cc: pce@ietf.org Subject: [Pce] Request for early allocation of code points for draft-ietf-p= ce-inter-layer-ext & status of draft Dear authors of draft-ietf-pce-inter-layer-ext, The draft draft-ietf-pce-inter-layer-ext, in its version 8 right now, intro= duces a set of new PCEP objects, which require object-class values. Current= recommended values clash with already allocated values. As suggested in the last IETF meeting in Toronto, the use of the early allo= cation procedure is recommended to handle the code points (when the draft i= s stable). Would it be possible that authors of the draft ask for early all= ocation of code points for draft-ietf-pce-inter-layer-ext ? On the other hand, I see that the draft has been stable for a while and eve= n has expired. Who is taking care of the updates of the draft? Is the draft= going to last call in the near future? Are you expecting a review? Best Regards, =D3scar ________________________________ Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, pu= ede contener informaci=F3n privilegiada o confidencial y es para uso exclus= ivo de la persona o entidad de destino. Si no es usted. el destinatario ind= icado, queda notificado de que la lectura, utilizaci=F3n, divulgaci=F3n y/o= copia sin autorizaci=F3n puede estar prohibida en virtud de la legislaci= =F3n vigente. Si ha recibido este mensaje por error, le rogamos que nos lo = comunique inmediatamente por esta misma v=EDa y proceda a su destrucci=F3n. The information contained in this transmission is privileged and confidenti= al information intended only for the use of the individual or entity named = above. If the reader of this message is not the intended recipient, you are= hereby notified that any dissemination, distribution or copying of this co= mmunication is strictly prohibited. If you have received this transmission = in error, do not read it. Please immediately reply to the sender that you h= ave received this communication in error and then delete it. Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat=E1rio= , pode conter informa=E7=E3o privilegiada ou confidencial e =E9 para uso ex= clusivo da pessoa ou entidade de destino. Se n=E3o =E9 vossa senhoria o des= tinat=E1rio indicado, fica notificado de que a leitura, utiliza=E7=E3o, div= ulga=E7=E3o e/ou c=F3pia sem autoriza=E7=E3o pode estar proibida em virtude= da legisla=E7=E3o vigente. Se recebeu esta mensagem por erro, rogamos-lhe = que nos o comunique imediatamente por esta mesma via e proceda a sua destru= i=E7=E3o ________________________________ Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, pu= ede contener informaci=F3n privilegiada o confidencial y es para uso exclus= ivo de la persona o entidad de destino. Si no es usted. el destinatario ind= icado, queda notificado de que la lectura, utilizaci=F3n, divulgaci=F3n y/o= copia sin autorizaci=F3n puede estar prohibida en virtud de la legislaci= =F3n vigente. Si ha recibido este mensaje por error, le rogamos que nos lo = comunique inmediatamente por esta misma v=EDa y proceda a su destrucci=F3n. The information contained in this transmission is privileged and confidenti= al information intended only for the use of the individual or entity named = above. If the reader of this message is not the intended recipient, you are= hereby notified that any dissemination, distribution or copying of this co= mmunication is strictly prohibited. If you have received this transmission = in error, do not read it. Please immediately reply to the sender that you h= ave received this communication in error and then delete it. Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat=E1rio= , pode conter informa=E7=E3o privilegiada ou confidencial e =E9 para uso ex= clusivo da pessoa ou entidade de destino. Se n=E3o =E9 vossa senhoria o des= tinat=E1rio indicado, fica notificado de que a leitura, utiliza=E7=E3o, div= ulga=E7=E3o e/ou c=F3pia sem autoriza=E7=E3o pode estar proibida em virtude= da legisla=E7=E3o vigente. Se recebeu esta mensagem por erro, rogamos-lhe = que nos o comunique imediatamente por esta mesma via e proceda a sua destru= i=E7=E3o --_000_7AEB3D6833318045B4AE71C2C87E8E1729C2D9C6dfweml706chm_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Hi Oscar and Fatai,<= /o:p>

 <= /p>

I think the special case = would be determined if the drafts have implementations that have been shipp= ed/deployed in production networks (which is above lab trials) prior to the standardization.  

 <= /p>

So any notes to the WG wi= th implementations in production networks will justify the early IANA alloc= ation.

 <= /p>

Regards,

Young

 <= /p>

From: Pce [mai= lto:pce-bounces@ietf.org] On Behalf Of OSCAR GONZALEZ DE DIOS
Sent: Friday, September 05, 2014 6:50 AM
To: Fatai Zhang; draft-ietf-pce-inter-layer-ext@tools.ietf.org
Cc: pce@ietf.org
Subject: Re: [Pce] Request for early allocation of code points for d= raft-ietf-pce-inter-layer-ext & status of draft

 

Hi Fatai,=

 

It is crystal clear that wh= en the document becomes an RFC, IANA will assign the correct number.

 

In my humble opinion, reque= sting for the early allocation is not “a special case”, but the= normal procedure that should be followed (obviously, it is not the traditional way to do things), approved by IANA, so early implementations = of stable documents have a code point that has no clashes. Furthermore, ear= ly allocated code points are maintained in the IANA registry. Traditional w= ay of adding the “suggested value” in the IANA section in the draft has led to many problems. We even have a = very recent case where a value used in a draft with early implementations h= as forced a value in an RFC with less implementations to change. =

 

    Summing up, I= see absolutely no reason not to ask for the early allocation, in this part= icular draft, and in all stable drafts in the working group. I the particular case of this drafts, the suggested values of the new objects ar= e the same ones are values used in existing RFCs, complicating the interope= rability. 

 

In any case, requesting the= early allocation is a decision to be taken by the authors of the draft. Ho= wever, I would like to know also the opinions of the chairs on wether the early allocation procedure is the “normal procedure= 221; or the “special case” for stable working group documents.<= o:p>

 

Best Regards,

 

=D3scar

 

     

 

De: Fatai Zhang <zhangfatai@huawei.com>
Fecha: viernes, 5 de septiembre de 2014 07:59
Para: Oscar Gonzalez de Dios <oscar.gonzalezdedios@telefonica.com>, "draft-ietf-pce= -inter-layer-ext@tools.ietf.org" <draft-ietf-pce-inter-layer-ext@tools.ie= tf.org>
CC: "pce@ietf.org" <= ;pce@ietf.org>
Asunto: RE: [Pce] Request for early allocation of code points for dr= aft-ietf-pce-inter-layer-ext & status of draft

 

Hi Oscar,

 

I don’t think we ne= ed to ask early allocation of code points, which is for the special case (i= e., early allocation is not the normal procedure) and the right values will be allocated during RFC publication stage (ie., the clash will= disappear) .

 

The authors of this draft= including me are taking care of this draft and we always welcome any revie= w comments from the WG.

 

Note that the WG chairs t= old in the previous meeting that they would like to move forward [draft-ietf-pce-gmpls-pcep-ex= tensions] first, and then move forward this draft.

 

Any further comments are apprecicated.

 

 

Best Regards

 

Fatai

 

From: Pce [mailto:pce-bou= nces@ietf.org] On Behalf Of OSCAR GONZALEZ DE DIOS
Sent: Thursday, September 04, 2014 6:00 PM
To: draft-ietf-pce-inter-layer-ext@tools.ietf.org
Cc: pce@ietf.org
Subject: [Pce] Request for early allocation of code points for draft= -ietf-pce-inter-layer-ext & status of draft

 =

Dear authors of draft-ietf-p= ce-inter-layer-ext,

 

The draft draft-ietf-pce-int= er-layer-ext, in its version 8 right now, introduces a set of new PCEP obje= cts, which require object-class values. Current recommended values clash with already allocated values.

 

As suggested in the last IET= F meeting in Toronto, the use of the early allocation procedure is recommen= ded to handle the code points (when the draft is stable). Would it be possible that authors of the draft ask for early allocati= on of code points for draft-ietf-pce-inter-layer-ext ?

 

On the other hand, I see tha= t the draft has been stable for a while and even has expired. Who is taking= care of the updates of the draft? Is the draft going to last call in the near future? Are you expecting a review?

 

Best Regards,

 

=D3scar 

 

 

 


Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, pu= ede contener informaci=F3n privilegiada o confidencial y es para uso exclus= ivo de la persona o entidad de destino. Si no es usted. el destinatario ind= icado, queda notificado de que la lectura, utilizaci=F3n, divulgaci=F3n y/o copia sin autorizaci=F3n puede e= star prohibida en virtud de la legislaci=F3n vigente. Si ha recibido este m= ensaje por error, le rogamos que nos lo comunique inmediatamente por esta m= isma v=EDa y proceda a su destrucci=F3n.

The information contained in this transmission is privileged and confidenti= al information intended only for the use of the individual or entity named = above. If the reader of this message is not the intended recipient, you are= hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If y= ou have received this transmission in error, do not read it. Please immedia= tely reply to the sender that you have received this communication in error= and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat=E1rio= , pode conter informa=E7=E3o privilegiada ou confidencial e =E9 para uso ex= clusivo da pessoa ou entidade de destino. Se n=E3o =E9 vossa senhoria o des= tinat=E1rio indicado, fica notificado de que a leitura, utiliza=E7=E3o, divulga=E7=E3o e/ou c=F3pia sem autoriza=E7=E3o p= ode estar proibida em virtude da legisla=E7=E3o vigente. Se recebeu esta me= nsagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mes= ma via e proceda a sua destrui=E7=E3o

 


Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, pu= ede contener informaci=F3n privilegiada o confidencial y es para uso exclus= ivo de la persona o entidad de destino. Si no es usted. el destinatario ind= icado, queda notificado de que la lectura, utilizaci=F3n, divulgaci=F3n y/o copia sin autorizaci=F3n puede e= star prohibida en virtud de la legislaci=F3n vigente. Si ha recibido este m= ensaje por error, le rogamos que nos lo comunique inmediatamente por esta m= isma v=EDa y proceda a su destrucci=F3n.

The information contained in this transmission is privileged and confidenti= al information intended only for the use of the individual or entity named = above. If the reader of this message is not the intended recipient, you are= hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If y= ou have received this transmission in error, do not read it. Please immedia= tely reply to the sender that you have received this communication in error= and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat=E1rio= , pode conter informa=E7=E3o privilegiada ou confidencial e =E9 para uso ex= clusivo da pessoa ou entidade de destino. Se n=E3o =E9 vossa senhoria o des= tinat=E1rio indicado, fica notificado de que a leitura, utiliza=E7=E3o, divulga=E7=E3o e/ou c=F3pia sem autoriza=E7=E3o p= ode estar proibida em virtude da legisla=E7=E3o vigente. Se recebeu esta me= nsagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mes= ma via e proceda a sua destrui=E7=E3o<= /o:p>

--_000_7AEB3D6833318045B4AE71C2C87E8E1729C2D9C6dfweml706chm_-- From nobody Sun Sep 7 10:39:25 2014 Return-Path: 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 550C11A048F for ; Sun, 7 Sep 2014 10:39:23 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.553 X-Spam-Level: X-Spam-Status: No, score=-3.553 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-1.652, 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 oWpYbagq4c90 for ; Sun, 7 Sep 2014 10:39:21 -0700 (PDT) Received: from smtptc.telefonica.com (smtptc.telefonica.com [195.76.34.108]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A37B11A0487 for ; Sun, 7 Sep 2014 10:39:20 -0700 (PDT) Received: from smtptc.telefonica.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 6EC39600AC; Sun, 7 Sep 2014 19:39:17 +0200 (CEST) Received: from ESTGVMSP104.EUROPE.telefonica.corp (unknown [10.92.4.9]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtptc.telefonica.com (Postfix) with ESMTPS id 52A99600A5; Sun, 7 Sep 2014 19:39:17 +0200 (CEST) Received: from emea01-am1-obe.outbound.protection.outlook.com (10.92.5.139) by tls.telefonica.com (10.93.6.50) with Microsoft SMTP Server (TLS) id 14.3.146.2; Sun, 7 Sep 2014 19:39:16 +0200 Received: from DB3PR06MB252.eurprd06.prod.outlook.com (10.141.5.153) by DB3PR06MB250.eurprd06.prod.outlook.com (10.141.5.141) with Microsoft SMTP Server (TLS) id 15.0.1024.12; Sun, 7 Sep 2014 17:38:14 +0000 Received: from DB3PR06MB252.eurprd06.prod.outlook.com ([10.141.5.153]) by DB3PR06MB252.eurprd06.prod.outlook.com ([10.141.5.153]) with mapi id 15.00.1024.012; Sun, 7 Sep 2014 17:38:14 +0000 From: DIEGO LOPEZ GARCIA To: Qin Wu Thread-Topic: [Pce] I-D Action: draft-wu-pce-discovery-pceps-support-01.txt Thread-Index: AQHPt34VeZpZpUDEXk+lwdwtWfp7gZvkTWGggANFqOCAAA1fsIAAHSNAgACpGzCADa9gAA== Date: Sun, 7 Sep 2014 17:38:14 +0000 Message-ID: References: <1B502206DFA0C544B7A60469152008633F36931A@eusaamb105.ericsson.se> <1B502206DFA0C544B7A60469152008633F3693C8@eusaamb105.ericsson.se> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [87.215.30.202] x-microsoft-antispam: BCL:0;PCL:0;RULEID:;UriScan:; x-forefront-prvs: 0327618309 x-forefront-antispam-report: SFV:NSPM; SFS:(10019017)(6009001)(189002)(199003)(252514010)(51704005)(24454002)(36756003)(97736003)(15202345003)(21056001)(81542001)(77982001)(46102001)(76482001)(80022001)(20776003)(81342001)(66066001)(87936001)(74662001)(79102001)(101416001)(85852003)(86362001)(83072002)(92726001)(92566001)(54356999)(31966008)(74502001)(4396001)(64706001)(99396002)(76176999)(50986999)(19580395003)(83322001)(19580405001)(82746002)(15975445006)(95666004)(2656002)(83716003)(90102001)(106356001)(85306004)(33656002)(93886004)(230783001)(105586002)(106116001)(110136001)(107046002)(104396001); DIR:OUT; SFP:1102; SCL:1; SRVR:DB3PR06MB250; H:DB3PR06MB252.eurprd06.prod.outlook.com; FPR:; MLV:sfv; PTR:InfoNoRecords; MX:1; A:1; LANG:en; Content-Type: text/plain; charset="utf-8" Content-ID: <2FC988D963AE964899F2E32FDE0E5231@eurprd06.prod.outlook.com> Content-Transfer-Encoding: base64 MIME-Version: 1.0 X-OriginatorOrg: telefonica.com X-TM-AS-MML: No Archived-At: http://mailarchive.ietf.org/arch/msg/pce/8rSB4z8dj5hUl2tLBeNpBOLFjFs Cc: "pce@ietf.org" Subject: Re: [Pce] I-D Action: draft-wu-pce-discovery-pceps-support-01.txt X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Sep 2014 17:39:23 -0000 DQpPbiAzMCBBdWcgMjAxNCwgYXQgMDI6NTYgLCBRaW4gV3UgPGJpbGwud3VAaHVhd2VpLmNvbT4g d3JvdGU6DQo+IFdlIGhhdmUgb25lIHVuZmluaXNoZWQgd29yayBpbiBLQVJQIGh0dHA6Ly90b29s cy5pZXRmLm9yZy9odG1sL2RyYWZ0LWNodW5kdXJpLWthcnAta21wLXJvdXRlci1maW5nZXJwcmlu dHMtMDUgd2hlcmUgd2UgcHJlY2lzZWx5IGFkZHJlc3MgdGhpcyB3aXRoIGZpbmdlciBwcmludHMg YmFzZWQgYXV0aGVudGljYXRpb24gZm9yIFRDUC1BTy9LTVAgYW5kIHRoZXNlIHByb2NlZHVyZXMg Y2FuIGJlIGV4dGVuZGFibGUgYW5kIGFwcGxpY2FibGUgdG8gVExTIGVhc2lseSBmb3IgUENFUCAo YXMgTUQgaXMgdGhlb3JldGljYWxseSBvYnNvbGV0ZSEpLCBkaXNjdXNzZWQgb2ZmbGluZSBmZXcg bW9udGhzIGFnby4NCj4gQXV0byBkaXNjb3ZlcnkgbWVjaGFuaXNtcyBldmVudHVhbGx5IHdpbGwg YmUgcmVhbGx5IGhlbHBmdWwgb25seSB3aGVuIHdlIGhhdmUgdGhlc2UgbWVjaGFuaXNtcyBpbiBw bGFjZSBwZXJoYXBzLg0KPg0KPiBbUWluXTogSW50ZXJlc3RpbmcuIFRoYW5rcyBmb3IgdmFsdWFi bGUgaW5mb3JtYXRpb24uDQoNCkp1c3QgdG8gcmVtYXJrIHRoYXQgSSBkaXNjdXNzZWQgdGhpcyBv cHRpb24gd2l0aCBVbWEgc29tZSB0aW1lIGFnby4gQXMgZmFyIGFzIEkgY2FuIHRlbGwsIHRoZSBQ Q0VQUyBkcmFmdCBkb2VzIG5vdCBwcmVjbHVkZSB0aGUgdXNhZ2Ugb2YgdGhlIGZpbmdlcnByaW50 aW5nIG1lY2hhbmlzbXMgZGVmaW5lZCBpbiBkcmFmdC1jaHVuZHVyaS1rYXJwLWttcC1yb3V0ZXIt ZmluZ2VycHJpbnRzLCBidXQgb24gdGhlIGNvbnRyYXJ5IGtleSBtYW5hZ2VtZW50IGNhbiBiZSBz aW1wbGlmaWVkIGJ5IGNvbWJpbmluZyBpdCB3aXRoIHRoZSBwcm9wb3NlZCBkaXNjb3ZlcnkgbWV0 aG9kLi4uDQoNCkJlIGdvb2RlLA0KDQotLQ0KUExFQVNFIE5PVEUgTVkgTkVXIEVNQUlMIEFERFJF U1MNCiJFc3RhIHZleiBubyBmYWxsYXJlbW9zLCBEb2N0b3IgSW5maWVybm8iDQoNCkRyIERpZWdv IFIuIExvcGV6DQpUZWxlZm9uaWNhIEkrRA0KaHR0cDovL3Blb3BsZS50aWQuZXMvZGllZ28ubG9w ZXovDQoNCmUtbWFpbDogZGllZ28uci5sb3BlekB0ZWxlZm9uaWNhLmNvbQ0KVGVsOiAgICArMzQg OTEzIDEyOSAwNDENCk1vYmlsZTogKzM0IDY4MiAwNTEgMDkxDQotLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tDQoNCg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCg0K RXN0ZSBtZW5zYWplIHkgc3VzIGFkanVudG9zIHNlIGRpcmlnZW4gZXhjbHVzaXZhbWVudGUgYSBz dSBkZXN0aW5hdGFyaW8sIHB1ZWRlIGNvbnRlbmVyIGluZm9ybWFjacOzbiBwcml2aWxlZ2lhZGEg byBjb25maWRlbmNpYWwgeSBlcyBwYXJhIHVzbyBleGNsdXNpdm8gZGUgbGEgcGVyc29uYSBvIGVu dGlkYWQgZGUgZGVzdGluby4gU2kgbm8gZXMgdXN0ZWQuIGVsIGRlc3RpbmF0YXJpbyBpbmRpY2Fk bywgcXVlZGEgbm90aWZpY2FkbyBkZSBxdWUgbGEgbGVjdHVyYSwgdXRpbGl6YWNpw7NuLCBkaXZ1 bGdhY2nDs24geS9vIGNvcGlhIHNpbiBhdXRvcml6YWNpw7NuIHB1ZWRlIGVzdGFyIHByb2hpYmlk YSBlbiB2aXJ0dWQgZGUgbGEgbGVnaXNsYWNpw7NuIHZpZ2VudGUuIFNpIGhhIHJlY2liaWRvIGVz dGUgbWVuc2FqZSBwb3IgZXJyb3IsIGxlIHJvZ2Ftb3MgcXVlIG5vcyBsbyBjb211bmlxdWUgaW5t ZWRpYXRhbWVudGUgcG9yIGVzdGEgbWlzbWEgdsOtYSB5IHByb2NlZGEgYSBzdSBkZXN0cnVjY2nD s24uDQoNClRoZSBpbmZvcm1hdGlvbiBjb250YWluZWQgaW4gdGhpcyB0cmFuc21pc3Npb24gaXMg cHJpdmlsZWdlZCBhbmQgY29uZmlkZW50aWFsIGluZm9ybWF0aW9uIGludGVuZGVkIG9ubHkgZm9y IHRoZSB1c2Ugb2YgdGhlIGluZGl2aWR1YWwgb3IgZW50aXR5IG5hbWVkIGFib3ZlLiBJZiB0aGUg cmVhZGVyIG9mIHRoaXMgbWVzc2FnZSBpcyBub3QgdGhlIGludGVuZGVkIHJlY2lwaWVudCwgeW91 IGFyZSBoZXJlYnkgbm90aWZpZWQgdGhhdCBhbnkgZGlzc2VtaW5hdGlvbiwgZGlzdHJpYnV0aW9u IG9yIGNvcHlpbmcgb2YgdGhpcyBjb21tdW5pY2F0aW9uIGlzIHN0cmljdGx5IHByb2hpYml0ZWQu IElmIHlvdSBoYXZlIHJlY2VpdmVkIHRoaXMgdHJhbnNtaXNzaW9uIGluIGVycm9yLCBkbyBub3Qg cmVhZCBpdC4gUGxlYXNlIGltbWVkaWF0ZWx5IHJlcGx5IHRvIHRoZSBzZW5kZXIgdGhhdCB5b3Ug aGF2ZSByZWNlaXZlZCB0aGlzIGNvbW11bmljYXRpb24gaW4gZXJyb3IgYW5kIHRoZW4gZGVsZXRl IGl0Lg0KDQpFc3RhIG1lbnNhZ2VtIGUgc2V1cyBhbmV4b3Mgc2UgZGlyaWdlbSBleGNsdXNpdmFt ZW50ZSBhbyBzZXUgZGVzdGluYXTDoXJpbywgcG9kZSBjb250ZXIgaW5mb3JtYcOnw6NvIHByaXZp bGVnaWFkYSBvdSBjb25maWRlbmNpYWwgZSDDqSBwYXJhIHVzbyBleGNsdXNpdm8gZGEgcGVzc29h IG91IGVudGlkYWRlIGRlIGRlc3Rpbm8uIFNlIG7Do28gw6kgdm9zc2Egc2VuaG9yaWEgbyBkZXN0 aW5hdMOhcmlvIGluZGljYWRvLCBmaWNhIG5vdGlmaWNhZG8gZGUgcXVlIGEgbGVpdHVyYSwgdXRp bGl6YcOnw6NvLCBkaXZ1bGdhw6fDo28gZS9vdSBjw7NwaWEgc2VtIGF1dG9yaXphw6fDo28gcG9k ZSBlc3RhciBwcm9pYmlkYSBlbSB2aXJ0dWRlIGRhIGxlZ2lzbGHDp8OjbyB2aWdlbnRlLiBTZSBy ZWNlYmV1IGVzdGEgbWVuc2FnZW0gcG9yIGVycm8sIHJvZ2Ftb3MtbGhlIHF1ZSBub3MgbyBjb211 bmlxdWUgaW1lZGlhdGFtZW50ZSBwb3IgZXN0YSBtZXNtYSB2aWEgZSBwcm9jZWRhIGEgc3VhIGRl c3RydWnDp8Ojbw0K From nobody Wed Sep 10 12:09:49 2014 Return-Path: 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 731401A001E for ; Wed, 10 Sep 2014 12:09:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.749 X-Spam-Level: X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no 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 wmUuiesBYqVV for ; Wed, 10 Sep 2014 12:09:47 -0700 (PDT) Received: from mail-wg0-x22c.google.com (mail-wg0-x22c.google.com [IPv6:2a00:1450:400c:c00::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 16F7C1A000B for ; Wed, 10 Sep 2014 12:09:46 -0700 (PDT) Received: by mail-wg0-f44.google.com with SMTP id y10so4592967wgg.15 for ; Wed, 10 Sep 2014 12:09:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=7pXr199V8KZROYNqdONbsRv5TxhGDExlWByeqePxL/s=; b=KU7SD+ekky5f3uuf1wpX6+lS70OAGUiWkZY0AeXrR8QsiiXUMzsYoWA8IFJEAecSiA paYDmuYu7ZcSS8EhXXeKSqUp2nm9pyW6LaZasahUV1E7E9Msjwd5KSttMhsC8YloaiT7 z7rYeer+fHlV4xsSqXbfqFh9vpEZVHCz1Sm9E/N9LFh3Z5cswIvGsz5syqI20HiIM2Y2 Chr031zCCPhkCnOZb8vWwVca6jUrYyK/DY2ysTC57NfQ1xu8yGJ2wXdVBGJ/SO07DeXD UKi3Z36HrGE0ZkZVItRVOyN1GPlTxz8xkbP1gPyIjXRFH9Amkfx8j/kmkYJECOeAcjHY Jh6g== MIME-Version: 1.0 X-Received: by 10.180.35.133 with SMTP id h5mr1779130wij.74.1410376185667; Wed, 10 Sep 2014 12:09:45 -0700 (PDT) Received: by 10.194.201.193 with HTTP; Wed, 10 Sep 2014 12:09:45 -0700 (PDT) Date: Wed, 10 Sep 2014 15:09:45 -0400 Message-ID: From: Samjhana Pokhrel To: pce@ietf.org Content-Type: multipart/alternative; boundary=e89a8f8391bf8be86a0502bacbdc Archived-At: http://mailarchive.ietf.org/arch/msg/pce/c3rGQJWTzYuLmrzzfpRgVAcE4Lo Subject: [Pce] SDN/MPLS 2014 Conference X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Sep 2014 19:09:48 -0000 --e89a8f8391bf8be86a0502bacbdc Content-Type: text/plain; charset=UTF-8 The SDN/MPLS 2014 Conference will take place November 2-5 in Washington DC and will include an extensive four day program consisting of tutorials, technical sessions, panels, and exhibits. The key topics to be discussed at this year's conference include: Virtualization, SDN, Cloud and Data Centers, NFV, PCE, Mobility, Traffic Engineering, Transport SDN, Orchestration, multi-play applications across common infrastructure and other emerging technologies. The SDN/MPLS 2014 Conference program is available at http://www.isocore.com/sdn-mpls/ *Tutorials (Sunday)*: http://www.isocore.com/sdn-mpls/tutorials.htm *Technical sessions (Mon- Wed)**:* http://www.isocore.com/sdn-mpls/technical_sessions.htm Please make sure to register for the SDN/MPLS 2014 by *September 15* for reduced rate registration. Please do so at: *http://www.isocore.com/sdn-mpls/attendees.php * Lastly, the conference hotel is the Marriott Wardman Park in Washington DC. Please note discounted rates are available for a limited time only. Please book your reservations at: https://resweb.passkey.com/Resweb.do?mode=welcome_gi_new&groupID=25088120 --e89a8f8391bf8be86a0502bacbdc Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
=C2=A0

The SD= N/MPLS 2014 Conference will take place November 2-5 in Washington DC and will
include an extensive four day program consisting of tutorials, technical sessions, panels, and exhibits. The key topics to be discussed at this
year's conference include: Virtualization, SDN, Cloud and Data Centers,= NFV,
PCE, Mobility, Traffic Engineering, Transport SDN, Orchestration,
multi-play applications across common infrastructure and other emerging technologies.

=C2=A0

The SDN/MPLS 2014 Conference program is available at http://www.iso= core.com/sdn-mpls/
Tutorials (Sunday): http://www.isocore.com/sdn-mpls/tutorials.htm
Technical sessions (Mon- Wed): http://www.isocore.com/sdn-mpls/techn= ical_sessions.htm

Please make sure to register for the SDN/MPLS 2014 by September 15 f= or reduced rate registration. Please do so at:

http://www.isocore.com/sdn-mp= ls/attendees.php

Lastly, the conference hotel is the Marriott Wardman Park in Washington DC. Please
note discounted rates are available for a limited time only. Please book yo= ur

reservations at:

https://resweb.passkey.com/Resweb.do?mode=3Dwelcome_gi_new&groupI= D=3D25088120
--e89a8f8391bf8be86a0502bacbdc-- From nobody Thu Sep 11 02:35:51 2014 Return-Path: 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 9C7E21A06AD; Thu, 11 Sep 2014 02:35:47 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 kGnai9xWv1Ui; Thu, 11 Sep 2014 02:35:46 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 210F31A069E; Thu, 11 Sep 2014 02:35:46 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 5.6.2.p6 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20140911093546.10155.7087.idtracker@ietfa.amsl.com> Date: Thu, 11 Sep 2014 02:35:46 -0700 Archived-At: http://mailarchive.ietf.org/arch/msg/pce/XYw9Yl7kVGxdzK5LR1Y1vU5NB_U Cc: pce@ietf.org Subject: [Pce] I-D Action: draft-ietf-pce-pceps-01.txt X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Sep 2014 09:35:48 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Path Computation Element Working Group of the IETF. Title : Secure Transport for PCEP Authors : Diego R. Lopez Oscar Gonzalez de Dios Qin Wu Dhruv Dhody Filename : draft-ietf-pce-pceps-01.txt Pages : 12 Date : 2014-09-11 Abstract: The Path Computation Element Communication Protocol (PCEP) defines the mechanisms for the communication between a Path Computation Client (PCC) and a Path Computation Element (PCE), or among PCEs. This document describe the usage of Transport Layer Security (TLS) to enhance PCEP security, hence the PCEPS acronym proposed for it. The additional security mechanisms are provided by the transport protocol supporting PCEP, and therefore they do not affect its flexibility and extensibility. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-pce-pceps/ There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-pce-pceps-01 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=draft-ietf-pce-pceps-01 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/ From nobody Thu Sep 11 02:37:03 2014 Return-Path: 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 3AC031A001E for ; Wed, 10 Sep 2014 12:08:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.552 X-Spam-Level: X-Spam-Status: No, score=-3.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-1.652, 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 RXnY3pvlbhQX for ; Wed, 10 Sep 2014 12:08:29 -0700 (PDT) Received: from server.isocore.com (server.isocore.com [192.163.204.174]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D708C1A86EB for ; Wed, 10 Sep 2014 12:08:07 -0700 (PDT) Received: from [65.213.193.24] (port=49468 helo=adminPCR) by server.isocore.com with esmtpa (Exim 4.82) (envelope-from ) id 1XRnFK-0001bU-Ml for Pce@ietf.org; Wed, 10 Sep 2014 19:08:02 +0000 From: "Shamjhana" To: Date: Wed, 10 Sep 2014 15:07:52 -0400 Message-ID: <003501cfcd2a$85db5c60$91921520$@isocore.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0036_01CFCD08.FECAF4E0" X-Mailer: Microsoft Outlook 14.0 Thread-Index: Ac/NKoHzm7e0Jy2mRbaMEcVc9eXGcg== Content-Language: en-us X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - server.isocore.com X-AntiAbuse: Original Domain - ietf.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - isocore.com X-Get-Message-Sender-Via: server.isocore.com: authenticated_id: spokharel@isocore.com X-Source: X-Source-Args: X-Source-Dir: Archived-At: http://mailarchive.ietf.org/arch/msg/pce/UTpUxmSPkzEfo-ETMYzlczmEb-g X-Mailman-Approved-At: Thu, 11 Sep 2014 02:36:44 -0700 Subject: [Pce] SDN/MPLS 2014 Conference X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Sep 2014 19:08:33 -0000 This is a multipart message in MIME format. ------=_NextPart_000_0036_01CFCD08.FECAF4E0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit The SDN/MPLS 2014 Conference will take place November 2-5 in Washington DC and will include an extensive four day program consisting of tutorials, technical sessions, panels, and exhibits. The key topics to be discussed at this year's conference include: Virtualization, SDN, Cloud and Data Centers, NFV, PCE, Mobility, Traffic Engineering, Transport SDN, Orchestration, multi-play applications across common infrastructure and other emerging technologies. The SDN/MPLS 2014 Conference program is available at http://www.isocore.com/sdn-mpls/ Tutorials (Sunday): http://www.isocore.com/sdn-mpls/tutorials.htm Technical sessions (Mon- Wed): http://www.isocore.com/sdn-mpls/technical_sessions.htm Please make sure to register for the SDN/MPLS 2014 by September 15 for reduced rate registration. Please do so at: http://www.isocore.com/sdn-mpls/attendees.php Lastly, the conference hotel is the Marriott Wardman Park in Washington DC. Please note discounted rates are available for a limited time only. Please book your reservations at: https://resweb.passkey.com/Resweb.do?mode=welcome_gi_new &groupID=25088120 ------=_NextPart_000_0036_01CFCD08.FECAF4E0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

The = SDN/MPLS 2014 Conference will take place November 2-5 in Washington DC = and will
include an extensive four day program consisting of = tutorials, technical
sessions, panels, and exhibits. The key topics = to be discussed at this
year's conference include: Virtualization, = SDN, Cloud and Data Centers, NFV,
PCE, Mobility, Traffic Engineering, = Transport SDN, Orchestration,
multi-play applications across common = infrastructure and other emerging technologies.

 

The SDN/MPLS = 2014 Conference program is = available at http://www.isocore.com/sdn-mpls= /
Tutorials (Sunday): http://www.isocore= .com/sdn-mpls/tutorials.htm
Technical sessions (Mon- = Wed): http://ww= w.isocore.com/sdn-mpls/technical_sessions.htm

Please make = sure to register for the SDN/MPLS 2014 by September 15 for = reduced rate registration. Please do so at:

http://www.isocore= .com/sdn-mpls/attendees.php

Lastly, the conference = hotel is the Marriott Wardman Park in Washington DC. Please
note = discounted rates are available for a limited time only. Please book your =

reservations at:

https://resweb.passkey.com/Resweb.do?mode=3Dwelcome_gi_= new&groupID=3D25088120

------=_NextPart_000_0036_01CFCD08.FECAF4E0-- From nobody Thu Sep 11 02:46:24 2014 Return-Path: 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 91B061A06BD for ; Thu, 11 Sep 2014 02:46:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.551 X-Spam-Level: X-Spam-Status: No, score=-3.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-1.652] 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 ZDD00DPwg0nf for ; Thu, 11 Sep 2014 02:46:16 -0700 (PDT) Received: from smtpjc.telefonica.com (smtpjc.telefonica.com [81.47.204.76]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D4E2E1A06B4 for ; Thu, 11 Sep 2014 02:46:15 -0700 (PDT) Received: from smtpjc.telefonica.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id D53212F015D for ; Thu, 11 Sep 2014 11:46:12 +0200 (CEST) Received: from ESTGVMSP114.EUROPE.telefonica.corp (unknown [10.92.4.9]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtpjc.telefonica.com (Postfix) with ESMTPS id B6B382F0125 for ; Thu, 11 Sep 2014 11:46:12 +0200 (CEST) Received: from emea01-db3-obe.outbound.protection.outlook.com (10.92.5.139) by tls.telefonica.com (10.93.6.55) with Microsoft SMTP Server (TLS) id 14.3.146.2; Thu, 11 Sep 2014 11:46:12 +0200 Received: from DB3PR06MB252.eurprd06.prod.outlook.com (10.141.5.153) by DB3PR06MB252.eurprd06.prod.outlook.com (10.141.5.153) with Microsoft SMTP Server (TLS) id 15.0.1024.12; Thu, 11 Sep 2014 09:46:10 +0000 Received: from DB3PR06MB252.eurprd06.prod.outlook.com ([10.141.5.153]) by DB3PR06MB252.eurprd06.prod.outlook.com ([10.141.5.153]) with mapi id 15.00.1024.012; Thu, 11 Sep 2014 09:46:10 +0000 From: DIEGO LOPEZ GARCIA To: "pce@ietf.org" Thread-Topic: [Pce] I-D Action: draft-ietf-pce-pceps-01.txt Thread-Index: AQHPzaPOFvMuyhzznEaOpWtWQdYatQ== Date: Thu, 11 Sep 2014 09:46:10 +0000 Message-ID: References: <20140911093546.10155.7087.idtracker@ietfa.amsl.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [83.51.57.162] x-microsoft-antispam: BCL:0;PCL:0;RULEID:;UriScan:; x-forefront-prvs: 03319F6FEF x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(377424004)(189002)(252514010)(199003)(2473001)(87936001)(85306004)(16236675004)(101416001)(33656002)(85852003)(83072002)(19580395003)(19580405001)(83322001)(107046002)(107886001)(2351001)(110136001)(36756003)(15202345003)(21056001)(230783001)(4396001)(90102001)(106116001)(106356001)(105586002)(19617315012)(77982001)(2501002)(97736003)(83716003)(79102001)(2656002)(86362001)(46102001)(50986999)(76176999)(54356999)(99396002)(95666004)(92566001)(92726001)(82746002)(31966008)(15975445006)(76482001)(74502001)(74662001)(80022001)(66066001)(81542001)(64706001)(81342001)(20776003)(104396001); DIR:OUT; SFP:1102; SCL:1; SRVR:DB3PR06MB252; H:DB3PR06MB252.eurprd06.prod.outlook.com; FPR:; PTR:InfoNoRecords; MX:1; A:1; LANG:en; received-spf: None (protection.outlook.com: telefonica.com does not designate permitted sender hosts) authentication-results: spf=none (sender IP is ) smtp.mailfrom=diego.r.lopez@telefonica.com; Content-Type: multipart/alternative; boundary="_000_CAA8C76DB1594831BA9991163E00A7A4telefonicacom_" MIME-Version: 1.0 X-OriginatorOrg: telefonica.com X-TM-AS-MML: No Archived-At: http://mailarchive.ietf.org/arch/msg/pce/hYrGQ6Y7jZCWBaVcz1hMGYF-b6I Subject: [Pce] Fwd: I-D Action: draft-ietf-pce-pceps-01.txt X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Sep 2014 09:46:19 -0000 --_000_CAA8C76DB1594831BA9991163E00A7A4telefonicacom_ Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi, This new version essentially introduces the idea of a StartTLS message, whi= ch was the agreement for TLS startup after the discussion of the draft with= Transport Area experts. A few aspects remain open for further experimentat= ion and refinement, though. Be goode, Begin forwarded message: From: > Subject: [Pce] I-D Action: draft-ietf-pce-pceps-01.txt Date: 11 September 2014 at 11:35:46.000 GMT+2 To: > Cc: > A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Path Computation Element Working Group of = the IETF. Title : Secure Transport for PCEP Authors : Diego R. Lopez Oscar Gonzalez de Dios Qin Wu Dhruv Dhody Filename : draft-ietf-pce-pceps-01.txt Pages : 12 Date : 2014-09-11 Abstract: The Path Computation Element Communication Protocol (PCEP) defines the mechanisms for the communication between a Path Computation Client (PCC) and a Path Computation Element (PCE), or among PCEs. This document describe the usage of Transport Layer Security (TLS) to enhance PCEP security, hence the PCEPS acronym proposed for it. The additional security mechanisms are provided by the transport protocol supporting PCEP, and therefore they do not affect its flexibility and extensibility. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-pce-pceps/ There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-pce-pceps-01 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-pce-pceps-01 Please note that it may take a couple of minutes from the time of submissio= n 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/ _______________________________________________ Pce mailing list Pce@ietf.org https://www.ietf.org/mailman/listinfo/pce -- PLEASE NOTE MY NEW EMAIL ADDRESS "Esta vez no fallaremos, Doctor Infierno" Dr Diego R. Lopez Telefonica I+D http://people.tid.es/diego.lopez/ e-mail: diego.r.lopez@telefonica.com Tel: +34 913 129 041 Mobile: +34 682 051 091 ---------------------------------- ________________________________ Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, pu= ede contener informaci=C3=B3n privilegiada o confidencial y es para uso exc= lusivo de la persona o entidad de destino. Si no es usted. el destinatario = indicado, queda notificado de que la lectura, utilizaci=C3=B3n, divulgaci= =C3=B3n y/o copia sin autorizaci=C3=B3n puede estar prohibida en virtud de = la legislaci=C3=B3n vigente. Si ha recibido este mensaje por error, le roga= mos que nos lo comunique inmediatamente por esta misma v=C3=ADa y proceda a= su destrucci=C3=B3n. The information contained in this transmission is privileged and confidenti= al information intended only for the use of the individual or entity named = above. If the reader of this message is not the intended recipient, you are= hereby notified that any dissemination, distribution or copying of this co= mmunication is strictly prohibited. If you have received this transmission = in error, do not read it. Please immediately reply to the sender that you h= ave received this communication in error and then delete it. Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat=C3=A1= rio, pode conter informa=C3=A7=C3=A3o privilegiada ou confidencial e =C3=A9= para uso exclusivo da pessoa ou entidade de destino. Se n=C3=A3o =C3=A9 vo= ssa senhoria o destinat=C3=A1rio indicado, fica notificado de que a leitura= , utiliza=C3=A7=C3=A3o, divulga=C3=A7=C3=A3o e/ou c=C3=B3pia sem autoriza= =C3=A7=C3=A3o pode estar proibida em virtude da legisla=C3=A7=C3=A3o vigent= e. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imedi= atamente por esta mesma via e proceda a sua destrui=C3=A7=C3=A3o --_000_CAA8C76DB1594831BA9991163E00A7A4telefonicacom_ Content-Type: text/html; charset="utf-8" Content-ID: Content-Transfer-Encoding: quoted-printable Hi,

This new version essentially introduces the idea of a StartTLS message= , which was the agreement for TLS startup after the discussion of the draft= with Transport Area experts. A few aspects remain open for further experim= entation and refinement, though.

Be goode,

Begin forwarded message:

Subject: [Pce] I-D Action: draft-ietf-pce-pceps-01.t= xt
Date: 11 September 2014 at 11:35:46.000 GMT+2
Cc: <pce@ietf.org= >


A New Internet-Draft is available from the on-line Internet-Drafts director= ies.
This draft is a work item of the Path Computation Element Working Group of = the IETF.

       Title     &nb= sp;     : Secure Transport for PCEP
       Authors     &= nbsp;   : Diego R. Lopez
            &nb= sp;            = Oscar Gonzalez de Dios
            &nb= sp;            = Qin Wu
            &nb= sp;            = Dhruv Dhody
Filename &n= bsp;      : draft-ietf-pce-pceps-01.txt
Pages  = ;         : 12
Date  =           : 2014-09-11
Abstract:
  The Path Computation Element Communication Protocol (PCEP) defi= nes
  the mechanisms for the communication between a Path Computation=
  Client (PCC) and a Path Computation Element (PCE), or among PCE= s.
  This document describe the usage of Transport Layer Security (T= LS) to
  enhance PCEP security, hence the PCEPS acronym proposed for it.=  The
  additional security mechanisms are provided by the transport pr= otocol
  supporting PCEP, and therefore they do not affect its flexibili= ty and
  extensibility.


The IETF datatracker status page for this draft is:
https://= datatracker.ietf.org/doc/draft-ietf-pce-pceps/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-pce-pceps-01

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-pce-pceps-01


Please note that it may take a couple of minutes from the time of submissio= n
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/

_______________________________________________
Pce mailing list
Pce@ietf.org
https://www.ietf.org/mailman/listinfo/pce

--
PLEASE NOTE MY NEW EMAIL ADDRESS
"Esta vez no fallaremos, Doctor Infierno"

Dr Diego R. Lopez
Telefonica I+D
http://people.tid.es/diego.lo= pez/

e-mail: diego.r.lopez@telefonica.com
Tel:    +34 913 129 041
Mobile: +34 682 051 091
----------------------------------



Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, pu= ede contener informaci=C3=B3n privilegiada o confidencial y es para uso exc= lusivo de la persona o entidad de destino. Si no es usted. el destinatario = indicado, queda notificado de que la lectura, utilizaci=C3=B3n, divulgaci=C3=B3n y/o copia sin autorizaci=C3=B3= n puede estar prohibida en virtud de la legislaci=C3=B3n vigente. Si ha rec= ibido este mensaje por error, le rogamos que nos lo comunique inmediatament= e por esta misma v=C3=ADa y proceda a su destrucci=C3=B3n.

The information contained in this transmission is privileged and confidenti= al information intended only for the use of the individual or entity named = above. If the reader of this message is not the intended recipient, you are= hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If y= ou have received this transmission in error, do not read it. Please immedia= tely reply to the sender that you have received this communication in error= and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat=C3=A1= rio, pode conter informa=C3=A7=C3=A3o privilegiada ou confidencial e =C3=A9= para uso exclusivo da pessoa ou entidade de destino. Se n=C3=A3o =C3=A9 vo= ssa senhoria o destinat=C3=A1rio indicado, fica notificado de que a leitura, utiliza=C3=A7=C3=A3o, divulga=C3=A7=C3=A3o e/ou c=C3=B3pia sem au= toriza=C3=A7=C3=A3o pode estar proibida em virtude da legisla=C3=A7=C3=A3o = vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique= imediatamente por esta mesma via e proceda a sua destrui=C3=A7=C3=A3o
 --_000_CAA8C76DB1594831BA9991163E00A7A4telefonicacom_-- From nobody Fri Sep 12 01:14:25 2014 Return-Path: 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 542FE1A0547 for ; Fri, 12 Sep 2014 01:14:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.852 X-Spam-Level: X-Spam-Status: No, score=-5.852 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-1.652, 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 7yqgfhqyM8ND for ; Fri, 12 Sep 2014 01:14:20 -0700 (PDT) Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 71E601A0203 for ; Fri, 12 Sep 2014 01:14:13 -0700 (PDT) Received: from 172.18.7.190 (EHLO lhreml403-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BMM03801; Fri, 12 Sep 2014 08:14:12 +0000 (GMT) Received: from NKGEML408-HUB.china.huawei.com (10.98.56.39) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 12 Sep 2014 09:14:11 +0100 Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.209]) by nkgeml408-hub.china.huawei.com ([10.98.56.39]) with mapi id 14.03.0158.001; Fri, 12 Sep 2014 16:13:59 +0800 From: Qin Wu To: "pce@ietf.org" Thread-Topic: Re: [Pce] I-D Action: draft-dw-pce-service-segment-routing-00.txt Thread-Index: Ac/OYYBePjCh6K9vQdmV6sB2EXo8xA== Date: Fri, 12 Sep 2014 08:13:58 +0000 Message-ID: Accept-Language: zh-CN, en-US Content-Language: zh-CN X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.138.41.180] Content-Type: multipart/alternative; boundary="_000_B8F9A780D330094D99AF023C5877DABA845C2CCAnkgeml501mbschi_" MIME-Version: 1.0 X-CFilter-Loop: Reflected Archived-At: http://mailarchive.ietf.org/arch/msg/pce/V02BNcea-M3zSCYj8V-8G3f0lms Subject: Re: [Pce] I-D Action: draft-dw-pce-service-segment-routing-00.txt X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Sep 2014 08:14:22 -0000 --_000_B8F9A780D330094D99AF023C5877DABA845C2CCAnkgeml501mbschi_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi,folks: Here is a new draft to discuss PCEP Extensions for service segment used in = Segment Routing. https://tools.ietf.org/html/draft-dw-pce-service-segment-routing-00 It extends SR-TE path defined in [I-D.sivabalan-pce-segment-routing] and allows a stateful PCE to compute and instantiate SR-TE paths that have service functions (SF) (or= service segments)involved. We like to solicit some review on this draft. Thanks! Regards! -Qin --_000_B8F9A780D330094D99AF023C5877DABA845C2CCAnkgeml501mbschi_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi,folks:

Here is a new draft to discuss PCEP Extensions fo=
r service segment used in Segment Routing.

https://tools.ietf.org/html/draft-dw-pce-service-segmen= t-routing-00

It extends SR-=
TE path defined in [I-D.sivabalan-pce-segment-routin=
g] and allows a stateful PCE 
to compute and=
 instantiate SR-TE paths that have service functions (SF) (or service segme=
nts)involved.
 
We like to sol=
icit some review on this draft. Thanks!
 
Regards!<=
/o:p>
-Qin
--_000_B8F9A780D330094D99AF023C5877DABA845C2CCAnkgeml501mbschi_-- From nobody Fri Sep 12 08:19:06 2014 Return-Path: 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 6D8F71A6F52 for ; Fri, 12 Sep 2014 08:19:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.536 X-Spam-Level: X-Spam-Status: No, score=-2.536 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, RP_MATCHES_RCVD=-1.652, SPF_SOFTFAIL=0.665] 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 2EAkp-kfXk82 for ; Fri, 12 Sep 2014 08:19:00 -0700 (PDT) Received: from r-mail2.rd.orange.com (r-mail2.rd.orange.com [217.108.152.42]) by ietfa.amsl.com (Postfix) with ESMTP id E2C4F1A6F14 for ; Fri, 12 Sep 2014 08:18:59 -0700 (PDT) Received: from r-mail2.rd.orange.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id AB01D5D89B7 for ; Fri, 12 Sep 2014 17:18:57 +0200 (CEST) Received: from ftrdsmtp2.rd.francetelecom.fr (unknown [10.192.128.47]) by r-mail2.rd.orange.com (Postfix) with ESMTP id 9FF8D5D8660 for ; Fri, 12 Sep 2014 17:18:57 +0200 (CEST) Received: from ftrdmel10.rd.francetelecom.fr ([10.192.128.44]) by ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.4675); Fri, 12 Sep 2014 17:18:56 +0200 Received: from [10.193.71.69] ([10.193.71.69]) by ftrdmel10.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.4675); Fri, 12 Sep 2014 17:18:56 +0200 Message-ID: <54130EE0.9070706@orange.com> Date: Fri, 12 Sep 2014 17:18:56 +0200 From: Julien Meuric Organization: Orange User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 To: pce@ietf.org References: In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit X-OriginalArrivalTime: 12 Sep 2014 15:18:56.0923 (UTC) FILETIME=[DF0A06B0:01CFCE9C] Archived-At: http://mailarchive.ietf.org/arch/msg/pce/dDIfNbjla-W9L7gglIgbT1moSg8 Subject: Re: [Pce] Request for early allocation of code points for draft-ietf-pce-inter-layer-ext & status of draft X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Sep 2014 15:19:03 -0000 Hi Oscar. Sorry for the late response, I have overlooked the part directed to the chairs. Even if suboptimal from the implementer's point of view, the usual procedure is codepoint allocation during RFC publication. Anyway, a process for early allocation is defined: as such, it is not a "special case" (a case without defined procedure would be), but not the mainstream procedure either. To correct one of your statement below, a WG I-D is owned by a WG. Requesting early allocation, as taking strong decisions related to a WG I-D, needs WG consensus (i.e. more than authors' decision). So far, no consensus for early allocation has been reached... Back to this particular I-D, suggested values are already out-dated and I am not sure a sudden "early" (or rather "late, but before RFC") allocation would bring much value at this stage. (But we may miss some information there.) Regards, Julien Sep. 05, 2014 - OSCAR GONZALEZ DE DIOS: > Hi Fatai, > > It is crystal clear that when the document becomes an RFC, IANA will > assign the correct number. > > In my humble opinion, requesting for the early allocation is not “a > special case”, but the normal procedure that should be followed > (obviously, it is not the traditional way to do things), approved by > IANA, so early implementations of stable documents have a code point > that has no clashes. Furthermore, early allocated code points are > maintained in the IANA registry. Traditional way of adding the > “suggested value” in the IANA section in the draft has led to many > problems. We even have a very recent case where a value used in a > draft with early implementations has forced a value in an RFC with > less implementations to change. > > Summing up, I see absolutely no reason not to ask for the early > allocation, in this particular draft, and in all stable drafts in the > working group. I the particular case of this drafts, the suggested > values of the new objects are the same ones are values used in > existing RFCs, complicating the interoperability. > > In any case, requesting the early allocation is a decision to be > taken by the authors of the draft. However, I would like to know also > the opinions of the chairs on wether the early allocation procedure > is the “normal procedure” or the “special case” for stable working > group documents. > > Best Regards, > > Óscar > > > > De: Fatai Zhang > Fecha: viernes, 5 de septiembre de > 2014 07:59 > > Hi Oscar, > > > > I don’t think we need to ask early allocation of code points, which > is for the special case (ie., early allocation is not the normal > procedure) and the right values will be allocated during RFC > publication stage (ie., the clash will disappear) . > > > > The authors of this draft including me are taking care of this draft > and we always welcome any review comments from the WG. > > > > Note that the WG chairs told in the previous meeting that they would > like to move forward [draft-ietf-pce-gmpls-pcep-extensions > ] > first, and then move forward this draft. > > > > Any further comments are apprecicated. > > > > > > Best Regards > > > > Fatai > > > > *From:*Pce [mailto:pce-bounces@ietf.org] *On Behalf Of *OSCAR > GONZALEZ DE DIOS *Sent:* Thursday, September 04, 2014 6:00 PM > > > > Dear authors of draft-ietf-pce-inter-layer-ext, > > > > The draft draft-ietf-pce-inter-layer-ext, in its version 8 right now, > introduces a set of new PCEP objects, which require object-class > values. Current recommended values clash with already allocated > values. > > > > As suggested in the last IETF meeting in Toronto, the use of the > early allocation procedure is recommended to handle the code points > (when the draft is stable). Would it be possible that authors of the > draft ask for early allocation of code points for > draft-ietf-pce-inter-layer-ext ? > > > > On the other hand, I see that the draft has been stable for a while > and even has expired. Who is taking care of the updates of the draft? > Is the draft going to last call in the near future? Are you expecting > a review? > > > > Best Regards, > > > > Óscar > > > > > > > > ------------------------- > > > Este mensaje y sus adjuntos se dirigen exclusivamente a su > destinatario, puede contener información privilegiada o confidencial > y es para uso exclusivo de la persona o entidad de destino. Si no es > usted. el destinatario indicado, queda notificado de que la lectura, > utilización, divulgación y/o copia sin autorización puede estar > prohibida en virtud de la legislación vigente. Si ha recibido este > mensaje por error, le rogamos que nos lo comunique inmediatamente por > esta misma vía y proceda a su destrucción. > > The information contained in this transmission is privileged and > confidential information intended only for the use of the individual > or entity named above. If the reader of this message is not the > intended recipient, you are hereby notified that any dissemination, > distribution or copying of this communication is strictly prohibited. > If you have received this transmission in error, do not read it. > Please immediately reply to the sender that you have received this > communication in error and then delete it. > > Esta mensagem e seus anexos se dirigem exclusivamente ao seu > destinatário, pode conter informação privilegiada ou confidencial e é > para uso exclusivo da pessoa ou entidade de destino. Se não é vossa > senhoria o destinatário indicado, fica notificado de que a leitura, > utilização, divulgação e/ou cópia sem autorização pode estar proibida > em virtude da legislação vigente. Se recebeu esta mensagem por erro, > rogamos-lhe que nos o comunique imediatamente por esta mesma via e > proceda a sua destruição > > > ------------------------- > > Este mensaje y sus adjuntos se dirigen exclusivamente a su > destinatario, puede contener información privilegiada o confidencial > y es para uso exclusivo de la persona o entidad de destino. Si no es > usted. el destinatario indicado, queda notificado de que la lectura, > utilización, divulgación y/o copia sin autorización puede estar > prohibida en virtud de la legislación vigente. Si ha recibido este > mensaje por error, le rogamos que nos lo comunique inmediatamente por > esta misma vía y proceda a su destrucción. > > The information contained in this transmission is privileged and > confidential information intended only for the use of the individual > or entity named above. If the reader of this message is not the > intended recipient, you are hereby notified that any dissemination, > distribution or copying of this communication is strictly prohibited. > If you have received this transmission in error, do not read it. > Please immediately reply to the sender that you have received this > communication in error and then delete it. > > Esta mensagem e seus anexos se dirigem exclusivamente ao seu > destinatário, pode conter informação privilegiada ou confidencial e é > para uso exclusivo da pessoa ou entidade de destino. Se não é vossa > senhoria o destinatário indicado, fica notificado de que a leitura, > utilização, divulgação e/ou cópia sem autorização pode estar proibida > em virtude da legislação vigente. Se recebeu esta mensagem por erro, > rogamos-lhe que nos o comunique imediatamente por esta mesma via e > proceda a sua destruição > > > _______________________________________________ Pce mailing list > Pce@ietf.org https://www.ietf.org/mailman/listinfo/pce From nobody Fri Sep 12 12:06:12 2014 Return-Path: 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 87F301A86F8 for ; Fri, 12 Sep 2014 12:06:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.552 X-Spam-Level: X-Spam-Status: No, score=-3.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-1.652] 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 2FcfMAauvh7E for ; Fri, 12 Sep 2014 12:06:03 -0700 (PDT) Received: from smtpjc.telefonica.com (smtpjc.telefonica.com [81.47.204.76]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 795901A8723 for ; Fri, 12 Sep 2014 12:05:52 -0700 (PDT) Received: from smtpjc.telefonica.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 688A42F013C; Fri, 12 Sep 2014 21:05:49 +0200 (CEST) Received: from ESTGVMSP114.EUROPE.telefonica.corp (unknown [10.92.4.9]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtpjc.telefonica.com (Postfix) with ESMTPS id 4CABE2F00A2; Fri, 12 Sep 2014 21:05:49 +0200 (CEST) Received: from emea01-db3-obe.outbound.protection.outlook.com (10.92.5.139) by tls.telefonica.com (10.93.6.55) with Microsoft SMTP Server (TLS) id 14.3.146.2; Fri, 12 Sep 2014 21:05:48 +0200 Received: from AMSPR06MB104.eurprd06.prod.outlook.com (10.242.90.155) by AMSPR06MB582.eurprd06.prod.outlook.com (10.242.23.156) with Microsoft SMTP Server (TLS) id 15.0.1024.12; Fri, 12 Sep 2014 19:05:48 +0000 Received: from AMSPR06MB104.eurprd06.prod.outlook.com (10.242.90.155) by AMSPR06MB104.eurprd06.prod.outlook.com (10.242.90.155) with Microsoft SMTP Server (TLS) id 15.0.1024.12; Fri, 12 Sep 2014 19:05:47 +0000 Received: from AMSPR06MB104.eurprd06.prod.outlook.com ([169.254.8.105]) by AMSPR06MB104.eurprd06.prod.outlook.com ([169.254.8.7]) with mapi id 15.00.1024.012; Fri, 12 Sep 2014 19:05:47 +0000 From: OSCAR GONZALEZ DE DIOS To: Julien Meuric , "pce@ietf.org" Thread-Topic: [Pce] Request for early allocation of code points for draft-ietf-pce-inter-layer-ext & status of draft Thread-Index: AQHPyM6nAMGlV8VNbU25ji56a2IqQZvyjv4AgAsZIQCAAGDpgA== Date: Fri, 12 Sep 2014 19:05:46 +0000 Message-ID: References: <54130EE0.9070706@orange.com> In-Reply-To: <54130EE0.9070706@orange.com> Accept-Language: es-ES, en-US Content-Language: es-ES X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.3.9.131030 x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [79.158.203.33] x-microsoft-antispam: BCL:0;PCL:0;RULEID:;UriScan:;UriScan:; x-forefront-prvs: 0332AACBC3 x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(189002)(52314003)(51914003)(199003)(51704005)(479174003)(377454003)(79102001)(77982001)(101416001)(83072002)(85852003)(19580405001)(83322001)(20776003)(74502001)(74662001)(31966008)(93886004)(66066001)(85306004)(80022001)(50986999)(92726001)(92566001)(76176999)(86362001)(54356999)(81542001)(81342001)(19580395003)(64706001)(99396002)(95666004)(4396001)(21056001)(2501002)(230783001)(97736003)(77096002)(2656002)(15202345003)(83506001)(15975445006)(106356001)(106116001)(105586002)(87936001)(90102001)(36756003)(46102001)(107886001)(107046002)(76482001); DIR:OUT; SFP:1102; SCL:1; SRVR:AMSPR06MB104; H:AMSPR06MB104.eurprd06.prod.outlook.com; FPR:; MLV:sfv; PTR:InfoNoRecords; MX:1; A:1; LANG:en; Content-Type: text/plain; charset="Windows-1252" Content-ID: <938EE3F2B97FA7418BFCE942096D32A2@eurprd06.prod.outlook.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:; X-OriginatorOrg: telefonica.com X-TM-AS-MML: No Archived-At: http://mailarchive.ietf.org/arch/msg/pce/HBg9fc10mx4OC80jzkYdnnLiGkM Subject: Re: [Pce] Request for early allocation of code points for draft-ietf-pce-inter-layer-ext & status of draft X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Sep 2014 19:06:08 -0000 Hi Julien Thanks for the answer, El 12/09/14 17:18, "Julien Meuric" escribi=F3: >Hi Oscar. > >Sorry for the late response, I have overlooked the part directed to the >chairs. > >Even if suboptimal from the implementer's point of view, the usual >procedure is codepoint allocation during RFC publication. Anyway, a >process for early allocation is defined: as such, it is not a "special >case" (a case without defined procedure would be), but not the >mainstream procedure either. RFC 7120 is the main source of information for the allocation procedure. The problem that such RFC tries to solve is when implementation and/or deployment experience are desired or required before the document becomes an RFC. Thus, it seems the mechanism is there for cases when there are early (pre-RFC) implementations, which are desired for feedback before the document becomes and RFC and changes are more difficult. Rest of cases when there are no pre-RFC implementations are OK with the usual procedure. > >To correct one of your statement below, a WG I-D is owned by a WG. >Requesting early allocation, as taking strong decisions related to a WG >I-D, needs WG consensus (i.e. more than authors' decision). Going back to RFC 7120, one of main thing to look at the early allocation in a draft is (again quoting) =B3The Working Group chairs and Area Director= s (ADs) judge that there is sufficient interest in the community for early (pre-RFC) implementation and deployment, or that failure to make an early allocation might lead to contention for the code point in the field." > So far, no >consensus for early allocation has been reached... Well.. I just noticed that there was a contention for the code point in the draft=8A so I just suggested the procedure to the authors, as a mean of help. One of the authors believed it was not necessary and standard procedure could be followed. > >Back to this particular I-D, suggested values are already out-dated and >I am not sure a sudden "early" (or rather "late, but before RFC") >allocation would bring much value at this stage. (But we may miss some >information there.) Well.. I think we were missing in previous email the spirit of RFC 7120. The information needed is whether there are early implementations or not. I guess that either the answer is no, or people are shy or not able to disclose it. > >Regards, > >Julien Best Regards, =D3scar > > >Sep. 05, 2014 - OSCAR GONZALEZ DE DIOS: >> Hi Fatai, > > > > It is crystal clear that when the document becomes an RFC, IANA will > > assign the correct number. > > > > In my humble opinion, requesting for the early allocation is not =B3a > > special case=B2, but the normal procedure that should be followed > > (obviously, it is not the traditional way to do things), approved by > > IANA, so early implementations of stable documents have a code point > > that has no clashes. Furthermore, early allocated code points are > > maintained in the IANA registry. Traditional way of adding the > > =B3suggested value=B2 in the IANA section in the draft has led to many > > problems. We even have a very recent case where a value used in a > > draft with early implementations has forced a value in an RFC with > > less implementations to change. > > > > Summing up, I see absolutely no reason not to ask for the early > > allocation, in this particular draft, and in all stable drafts in the > > working group. I the particular case of this drafts, the suggested > > values of the new objects are the same ones are values used in > > existing RFCs, complicating the interoperability. > > > > In any case, requesting the early allocation is a decision to be > > taken by the authors of the draft. However, I would like to know also > > the opinions of the chairs on wether the early allocation procedure > > is the =B3normal procedure=B2 or the =B3special case=B2 for stable work= ing > > group documents. > > > > Best Regards, > > > > =D3scar > > > > > > > > De: Fatai Zhang > > Fecha: viernes, 5 de septiembre de > > 2014 07:59 > > > > Hi Oscar, > > > > > > > > I don=B9t think we need to ask early allocation of code points, which > > is for the special case (ie., early allocation is not the normal > > procedure) and the right values will be allocated during RFC > > publication stage (ie., the clash will disappear) . > > > > > > > > The authors of this draft including me are taking care of this draft > > and we always welcome any review comments from the WG. > > > > > > > > Note that the WG chairs told in the previous meeting that they would > > like to move forward [draft-ietf-pce-gmpls-pcep-extensions > > ] > > first, and then move forward this draft. > > > > > > > > Any further comments are apprecicated. > > > > > > > > > > > > Best Regards > > > > > > > > Fatai > > > > > > > > *From:*Pce [mailto:pce-bounces@ietf.org] *On Behalf Of *OSCAR > > GONZALEZ DE DIOS *Sent:* Thursday, September 04, 2014 6:00 PM > > > > > > > > Dear authors of draft-ietf-pce-inter-layer-ext, > > > > > > > > The draft draft-ietf-pce-inter-layer-ext, in its version 8 right now, > > introduces a set of new PCEP objects, which require object-class > > values. Current recommended values clash with already allocated > > values. > > > > > > > > As suggested in the last IETF meeting in Toronto, the use of the > > early allocation procedure is recommended to handle the code points > > (when the draft is stable). Would it be possible that authors of the > > draft ask for early allocation of code points for > > draft-ietf-pce-inter-layer-ext ? > > > > > > > > On the other hand, I see that the draft has been stable for a while > > and even has expired. Who is taking care of the updates of the draft? > > Is the draft going to last call in the near future? Are you expecting > > a review? > > > > > > > > Best Regards, > > > > > > > > =D3scar > > > > > > > > > > > > > > > > ------------------------- > > > > > > Este mensaje y sus adjuntos se dirigen exclusivamente a su > > destinatario, puede contener informaci=F3n privilegiada o confidencial > > y es para uso exclusivo de la persona o entidad de destino. Si no es > > usted. el destinatario indicado, queda notificado de que la lectura, > > utilizaci=F3n, divulgaci=F3n y/o copia sin autorizaci=F3n puede estar > > prohibida en virtud de la legislaci=F3n vigente. Si ha recibido este > > mensaje por error, le rogamos que nos lo comunique inmediatamente por > > esta misma v=EDa y proceda a su destrucci=F3n. > > > > The information contained in this transmission is privileged and > > confidential information intended only for the use of the individual > > or entity named above. If the reader of this message is not the > > intended recipient, you are hereby notified that any dissemination, > > distribution or copying of this communication is strictly prohibited. > > If you have received this transmission in error, do not read it. > > Please immediately reply to the sender that you have received this > > communication in error and then delete it. > > > > Esta mensagem e seus anexos se dirigem exclusivamente ao seu > > destinat=E1rio, pode conter informa=E7=E3o privilegiada ou confidencial= e =E9 > > para uso exclusivo da pessoa ou entidade de destino. Se n=E3o =E9 vossa > > senhoria o destinat=E1rio indicado, fica notificado de que a leitura, > > utiliza=E7=E3o, divulga=E7=E3o e/ou c=F3pia sem autoriza=E7=E3o pode es= tar proibida > > em virtude da legisla=E7=E3o vigente. Se recebeu esta mensagem por erro= , > > rogamos-lhe que nos o comunique imediatamente por esta mesma via e > > proceda a sua destrui=E7=E3o > > > > > > ------------------------- > > > > Este mensaje y sus adjuntos se dirigen exclusivamente a su > > destinatario, puede contener informaci=F3n privilegiada o confidencial > > y es para uso exclusivo de la persona o entidad de destino. Si no es > > usted. el destinatario indicado, queda notificado de que la lectura, > > utilizaci=F3n, divulgaci=F3n y/o copia sin autorizaci=F3n puede estar > > prohibida en virtud de la legislaci=F3n vigente. Si ha recibido este > > mensaje por error, le rogamos que nos lo comunique inmediatamente por > > esta misma v=EDa y proceda a su destrucci=F3n. > > > > The information contained in this transmission is privileged and > > confidential information intended only for the use of the individual > > or entity named above. If the reader of this message is not the > > intended recipient, you are hereby notified that any dissemination, > > distribution or copying of this communication is strictly prohibited. > > If you have received this transmission in error, do not read it. > > Please immediately reply to the sender that you have received this > > communication in error and then delete it. > > > > Esta mensagem e seus anexos se dirigem exclusivamente ao seu > > destinat=E1rio, pode conter informa=E7=E3o privilegiada ou confidencial= e =E9 > > para uso exclusivo da pessoa ou entidade de destino. Se n=E3o =E9 vossa > > senhoria o destinat=E1rio indicado, fica notificado de que a leitura, > > utiliza=E7=E3o, divulga=E7=E3o e/ou c=F3pia sem autoriza=E7=E3o pode es= tar proibida > > em virtude da legisla=E7=E3o vigente. Se recebeu esta mensagem por erro= , > > rogamos-lhe que nos o comunique imediatamente por esta mesma via e > > proceda a sua destrui=E7=E3o > > > > > > _______________________________________________ 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 ________________________________ Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, pu= ede contener informaci=F3n privilegiada o confidencial y es para uso exclus= ivo de la persona o entidad de destino. Si no es usted. el destinatario ind= icado, queda notificado de que la lectura, utilizaci=F3n, divulgaci=F3n y/o= copia sin autorizaci=F3n puede estar prohibida en virtud de la legislaci= =F3n vigente. Si ha recibido este mensaje por error, le rogamos que nos lo = comunique inmediatamente por esta misma v=EDa y proceda a su destrucci=F3n. The information contained in this transmission is privileged and confidenti= al information intended only for the use of the individual or entity named = above. If the reader of this message is not the intended recipient, you are= hereby notified that any dissemination, distribution or copying of this co= mmunication is strictly prohibited. If you have received this transmission = in error, do not read it. Please immediately reply to the sender that you h= ave received this communication in error and then delete it. Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat=E1rio= , pode conter informa=E7=E3o privilegiada ou confidencial e =E9 para uso ex= clusivo da pessoa ou entidade de destino. Se n=E3o =E9 vossa senhoria o des= tinat=E1rio indicado, fica notificado de que a leitura, utiliza=E7=E3o, div= ulga=E7=E3o e/ou c=F3pia sem autoriza=E7=E3o pode estar proibida em virtude= da legisla=E7=E3o vigente. Se recebeu esta mensagem por erro, rogamos-lhe = que nos o comunique imediatamente por esta mesma via e proceda a sua destru= i=E7=E3o From nobody Sun Sep 14 03:06:34 2014 Return-Path: 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 6720D1A0304 for ; Sun, 14 Sep 2014 03:06:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -16.153 X-Spam-Level: X-Spam-Status: No, score=-16.153 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.652, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 cv4-u4ZCnt3W for ; Sun, 14 Sep 2014 03:06:26 -0700 (PDT) Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 88ECE1A0302 for ; Sun, 14 Sep 2014 03:06:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1287; q=dns/txt; s=iport; t=1410689186; x=1411898786; h=from:to:subject:date:message-id:mime-version; bh=SAfXkvwHZn6ShrepS4b8rvYItelBv4C0XoJVSQ3GPgI=; b=iF53lpd3Urk/N26vVAjNdORgvwxZGm4+7h27PToNYmkCst16Kd1Mbt5K QJTVhCAC02Krjg+y0fgu/P/ck2asSyUjAYzILripVV1kzV44E21Y6/k3O fsFERZ3xdl+4dYmmp/dKD3r0GRFKzvGp/lRMF0dR5cVhjcj2OhrZ+4Gu3 c=; X-Files: signature.asc : 496 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: As0LAGRnFVStJA2G/2dsb2JhbABggw2BLo1IxE8WeIQKgQsBgQAnBCGIMJJ4pD8BF5MCgR0FjzeCFoIIgUuHaJU/g16CNIECAQEB X-IronPort-AV: E=Sophos;i="5.04,520,1406592000"; d="asc'?scan'208";a="355164071" Received: from alln-core-12.cisco.com ([173.36.13.134]) by rcdn-iport-4.cisco.com with ESMTP; 14 Sep 2014 10:06:25 +0000 Received: from xhc-rcd-x04.cisco.com (xhc-rcd-x04.cisco.com [173.37.183.78]) by alln-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id s8EA6P2c003245 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for ; Sun, 14 Sep 2014 10:06:25 GMT Received: from xmb-rcd-x02.cisco.com ([169.254.4.5]) by xhc-rcd-x04.cisco.com ([fe80::200:5efe:173.37.183.34%12]) with mapi id 14.03.0195.001; Sun, 14 Sep 2014 05:06:25 -0500 From: "JP Vasseur (jvasseur)" To: "pce@ietf.org" Thread-Topic: Adoption of draft-sivabalan-pce-lsp-setup-type-02.txt as a PCE WG Document Thread-Index: AQHP0AOKhQXX3FptfUeVYEz+5mQyKQ== Date: Sun, 14 Sep 2014 10:06:24 +0000 Message-ID: <70E9F53F-3A40-4CC6-924B-9BA229FD84AA@cisco.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: x-originating-ip: [10.60.114.231] Content-Type: multipart/signed; boundary="Apple-Mail=_95879DDB-5205-4192-9C1A-6004A6197DCE"; protocol="application/pgp-signature"; micalg=pgp-sha512 MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/pce/KS8U8Fyk33Oxpkbwq2-S9gCP9Ws Subject: [Pce] Adoption of draft-sivabalan-pce-lsp-setup-type-02.txt as a PCE WG Document X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Sep 2014 10:06:31 -0000 --Apple-Mail=_95879DDB-5205-4192-9C1A-6004A6197DCE Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Dear WG, We had several discussions showing a good consensus adopting = draft-sivabalan-pce-lsp-setup-type-02.txt and this work has considerably progressed in other WG. Are you in favor of adopting draft-sivabalan-pce-lsp-setup-type-02.txt = as a PCE WG document ? Thanks. JP and Julien. --Apple-Mail=_95879DDB-5205-4192-9C1A-6004A6197DCE Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="signature.asc" Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQEcBAEBCgAGBQJUFWieAAoJEHBVWzpLl1Mt7EYH/jQF4TljzXc9ROryIFVJdrgP i4X7pcIE9Zu+T/y8RwF6hw6OCJVaIXbhLW74TrBg4gAf/A+whlOFqxyRWjPEXkEP Q8Dm+8GyyLQTQL2rllQpEHCGRig0QzvsF0g0NvazSicrHhbY5Qam1eb4fJ0Shdyz RnvGOkH/0nV1ylfyOzqiEHJcDDwG4JlcI0HCMzvEmIszeFbzr0HUFRvwo9kKmDpw GmErYE99rKVIIYmhM1pG2QS8/uAyEOwZhP9dUsWAFJMceXtilKVZJOcXzPc0bajH 5MndSLE0D0OG3F5S+UZSfQ+S0RmkaJ/bH+E9rT+jEi+pByLi9JLpuhjy/HdAsxc= =hrMs -----END PGP SIGNATURE----- --Apple-Mail=_95879DDB-5205-4192-9C1A-6004A6197DCE-- From nobody Sun Sep 14 03:06:57 2014 Return-Path: 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 545261A0304 for ; Sun, 14 Sep 2014 03:06:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -16.153 X-Spam-Level: X-Spam-Status: No, score=-16.153 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.652, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 XoViSKnSsuxQ for ; Sun, 14 Sep 2014 03:06:30 -0700 (PDT) Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BDAE01A0303 for ; Sun, 14 Sep 2014 03:06:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1295; q=dns/txt; s=iport; t=1410689189; x=1411898789; h=from:to:subject:date:message-id:mime-version; bh=0ypwYJbOH4f/PThPv8kXYkWabLWTlAYLriwydXQil/U=; b=fL4mlyCO+3t05cvs+nJs0+MZvgHGNVvqBrgpL6nzPwwE3+EscnwALCfe hMAfPlbmM6NwrZVUJFgmkjcpVonAWBXvFrniQ/DSRV54Rced6UHkhL/58 Nd1xz2lgsi6Pd585VSU4NQEv/6zgYgY7br8Ddv4wgh5+iQX0miUL3xIZg U=; X-Files: signature.asc : 496 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgEFAKBnFVStJV2R/2dsb2JhbABggw2BLtIXFniECoELAYEAJwQhiDCSeKQ/AReTAoEdBY83ghaCCIFLh2iVP4NegjSBAgEBAQ X-IronPort-AV: E=Sophos;i="5.04,520,1406592000"; d="asc'?scan'208";a="77707998" Received: from rcdn-core-9.cisco.com ([173.37.93.145]) by alln-iport-1.cisco.com with ESMTP; 14 Sep 2014 10:06:28 +0000 Received: from xhc-rcd-x09.cisco.com (xhc-rcd-x09.cisco.com [173.37.183.83]) by rcdn-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id s8EA6SOG031755 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for ; Sun, 14 Sep 2014 10:06:28 GMT Received: from xmb-rcd-x02.cisco.com ([169.254.4.5]) by xhc-rcd-x09.cisco.com ([173.37.183.83]) with mapi id 14.03.0195.001; Sun, 14 Sep 2014 05:06:28 -0500 From: "JP Vasseur (jvasseur)" To: "pce@ietf.org" Thread-Topic: Adopting of draft-sivabalan-pce-segment-routing-03.txt as PCE WG Document Thread-Index: AQHP0AOM1KLRLywSpUW4vDYHaosXcg== Date: Sun, 14 Sep 2014 10:06:28 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: x-originating-ip: [10.60.114.231] Content-Type: multipart/signed; boundary="Apple-Mail=_CCDCEF47-DAF9-4639-B309-78406E07A8B4"; protocol="application/pgp-signature"; micalg=pgp-sha512 MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/pce/9CuHmJGp7UwsYXt2sH-RTqfrgh4 Subject: [Pce] Adopting of draft-sivabalan-pce-segment-routing-03.txt as PCE WG Document X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Sep 2014 10:06:35 -0000 --Apple-Mail=_CCDCEF47-DAF9-4639-B309-78406E07A8B4 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Dear WG, We had several discussions showing a good consensus adopting = draft-sivabalan-pce-segment-routing-03.txt and this work has considerably progressed in other WG. Are you in favor of adopting draft-sivabalan-pce-segment-routing-03.txt = as a PCE WG document ? Thanks. JP and Julien. --Apple-Mail=_CCDCEF47-DAF9-4639-B309-78406E07A8B4 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="signature.asc" Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQEcBAEBCgAGBQJUFWikAAoJEHBVWzpLl1MtduUIAKMr2cXBVKUWoRKdDXNYFGd6 0THiW/5EpJYMySDH4QKmYqBa777ocpr6vVAad5Z+OuLwA4cWikxlRjGYTsTiSsJ/ CG90yKRZ+mH1yJJWsowYgCVt4OSQ8LG41DWGu/3cjGBKqIb0e7Q/RzdMjnlNMpbY Qxn1K1wGjxlyg7wyNJ9dLWRuN5deDI6QSHJfKpDDemtLzqayUQ8aVkeeRx2hCgZy m3MXuFU4kkkXcMJBSDpEBjrlkJRR/eiSb0hQ1xfQnmS+9crrblJU/4EUqYbTGnzG IVRbKwO59S00pWYcuqQC1VnGzsVvI7dm5vaoHQ5fn2pRMoPhTCI1VzAI0Lk+ofs= =Qsad -----END PGP SIGNATURE----- --Apple-Mail=_CCDCEF47-DAF9-4639-B309-78406E07A8B4-- From nobody Sun Sep 14 03:12:11 2014 Return-Path: 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 A62A01A0303 for ; Sun, 14 Sep 2014 03:12:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -16.152 X-Spam-Level: X-Spam-Status: No, score=-16.152 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.652, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 wVfKOPw80kGZ for ; Sun, 14 Sep 2014 03:12:07 -0700 (PDT) Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2F1A71A0302 for ; Sun, 14 Sep 2014 03:12:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2966; q=dns/txt; s=iport; t=1410689527; x=1411899127; h=from:to:subject:date:message-id:mime-version; bh=kQCMFvltAwlRPKtBiun9fWrFxRZjtgUxeNHBRvgG81c=; b=Xmwhh6qo/S44P2ZHoAiLnc+OGJnEaieXe5UuMVXfWkPN8EpsIMAfN4Dt 5a63GoPEWeriv/I64bkQjR/pCRZQ9nMGKrv1vi3fTskJu4i18Xb0rUnIp fSKorkQkcaznUFX1Net864NhGfg9Pnn35FYBCji3kZqcEJGEFOFeNYHh1 0=; X-Files: signature.asc : 496 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgEFAKVoFVStJV2S/2dsb2JhbABggw2BLtIXFniECm4dAQwBcycEIYgwknmkPwEXkwKBHQWPN4IWggiBS4dolT+CG4FDgjSBAgEBAQ X-IronPort-AV: E=Sophos;i="5.04,520,1406592000"; d="asc'?scan'208,217";a="77771047" Received: from rcdn-core-10.cisco.com ([173.37.93.146]) by alln-iport-7.cisco.com with ESMTP; 14 Sep 2014 10:12:06 +0000 Received: from xhc-rcd-x10.cisco.com (xhc-rcd-x10.cisco.com [173.37.183.84]) by rcdn-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id s8EAC6qW009232 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for ; Sun, 14 Sep 2014 10:12:06 GMT Received: from xmb-rcd-x02.cisco.com ([169.254.4.5]) by xhc-rcd-x10.cisco.com ([173.37.183.84]) with mapi id 14.03.0195.001; Sun, 14 Sep 2014 05:12:06 -0500 From: "JP Vasseur (jvasseur)" To: "pce@ietf.org" Thread-Topic: WG Last Call on draft-ietf-pce-stateful-pce-app-02 and draft-ietf-pce-stateful-pce-09 Thread-Index: AQHP0ARVQD5F3VY9REKwNcdOFPjV1A== Date: Sun, 14 Sep 2014 10:12:05 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: x-originating-ip: [10.60.114.231] Content-Type: multipart/signed; boundary="Apple-Mail=_C24AF5E6-5EA2-4B3A-8921-106CA81BE8E3"; protocol="application/pgp-signature"; micalg=pgp-sha512 MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/pce/fZj229_ECuai7MBLXyPjCQqy6JI Subject: [Pce] WG Last Call on draft-ietf-pce-stateful-pce-app-02 and draft-ietf-pce-stateful-pce-09 X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Sep 2014 10:12:08 -0000 --Apple-Mail=_C24AF5E6-5EA2-4B3A-8921-106CA81BE8E3 Content-Type: multipart/alternative; boundary="Apple-Mail=_E25DE49D-C947-47D5-9E12-AC522093C13F" --Apple-Mail=_E25DE49D-C947-47D5-9E12-AC522093C13F Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Dear WG, Both draft-ietf-pce-stateful-pce-app-02 and = draft-ietf-pce-stateful-pce-09 are now stable ready for WG Last Call. This starts a 3-week WG Last call, which will end on Oct 6 at noon ET. Please send your comments on the mailing list. ps: this WG LC will be followed by another WG LC on = draft-ietf-pce-stateful-sync-optimizations-01 and draft-ietf-pce-pce-initiated-lsp-01. Thanks. JP and Julien. --Apple-Mail=_E25DE49D-C947-47D5-9E12-AC522093C13F Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii Dear = WG,

Both draft-ietf-pce-stateful-pce-app-02 and = draft-ietf-pce-stateful-pce-09 are now stable ready for WG Last = Call.
This starts a 3-week WG Last call, which will end on = Oct 6 at noon ET.

Please send your = comments on the mailing list.

ps: this WG LC = will be followed by another WG LC on draft-ietf-pce-stateful-sync-optimizations-01
and&= nbsp;draft-ietf-pce-pce-initiated-lsp-01.


Thanks.

JP and = Julien.
= --Apple-Mail=_E25DE49D-C947-47D5-9E12-AC522093C13F-- --Apple-Mail=_C24AF5E6-5EA2-4B3A-8921-106CA81BE8E3 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="signature.asc" Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQEcBAEBCgAGBQJUFWnzAAoJEHBVWzpLl1MtEeMIAJVtD2fym6EeSew+0DtcYbnk PUrB70NaJlNxwpBiMGw4Qb5+0YWtJY2okAwOc5cgfcOA0VJywEq9clFxcOTZG8Hz BLW9tBBWDZdM90J0d+7DZSGSd/52CPZZKUCnr8AeK4gnvsjNXJHMRscGQapQ6NWt bbQEIlKYw6yF4MyeJqkWpl+yPSXyOJIOF3AneXijNgccQdJWk4T4UySoTZRNgxpg PA9f6ioTqtPVWVt8bZ8pwTcnn+UoyMTvuxUIyG3J25L8IkGxEQgBXUUsclASxpVm +GusUFT7ThdM4aVNlNKxTxeTvNnN7NSWGp9FmRdJi7fisn5+34WjnMeobdJigfk= =eknm -----END PGP SIGNATURE----- --Apple-Mail=_C24AF5E6-5EA2-4B3A-8921-106CA81BE8E3-- From nobody Sun Sep 14 06:54:26 2014 Return-Path: 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 772021A0391 for ; Sun, 14 Sep 2014 06:54:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -16.152 X-Spam-Level: X-Spam-Status: No, score=-16.152 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.652, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 pXcFqP1hRC31 for ; Sun, 14 Sep 2014 06:54:23 -0700 (PDT) Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E34E31A038A for ; Sun, 14 Sep 2014 06:54:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4341; q=dns/txt; s=iport; t=1410702863; x=1411912463; h=from:to:subject:date:message-id:references:mime-version; bh=1DD64IhAPwRfkJYsDs9ZX+MuTfnG2VA8pwuuPz3sDYs=; b=cLsZ8ZDQfieXyvzdTcz095UFrNFYCOWWra9apTgtZ4GIxAZy+9L2UEM+ FmlrVgV/DZs0tW3Megk1DAXVhFICs42ROGPC3errQXq9TM9tqljIuvQhf kaXPVYIMGj2/tLJNPFvM8efV8ZVCxgH92/KoQAj1DHfywMRP+SA7A3MfY I=; X-Files: signature.asc : 496 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgcFAImdFVStJV2c/2dsb2JhbABggw1TW8k6AQmHToEFFniEAwEBAQMBAQEBaxALAgEMDQMBAi8nCxsCCAIEEw6IKAgNt2QBEwSPPB6DKIEdBY83ghaCCIFLh2iVP4IbgUNsgUiBAgEBAQ X-IronPort-AV: E=Sophos;i="5.04,521,1406592000"; d="asc'?scan'208,217";a="355085259" Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-2.cisco.com with ESMTP; 14 Sep 2014 13:54:22 +0000 Received: from xhc-rcd-x15.cisco.com (xhc-rcd-x15.cisco.com [173.37.183.89]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id s8EDsMNV006137 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for ; Sun, 14 Sep 2014 13:54:22 GMT Received: from xmb-rcd-x02.cisco.com ([169.254.4.5]) by xhc-rcd-x15.cisco.com ([173.37.183.89]) with mapi id 14.03.0195.001; Sun, 14 Sep 2014 08:54:21 -0500 From: "JP Vasseur (jvasseur)" To: "pce@ietf.org" Thread-Topic: [Pce] Adopting of draft-sivabalan-pce-segment-routing-03.txt as PCE WG Document Thread-Index: AQHP0CNiCCtRNqCSWEqUClZSmzJWKQ== Date: Sun, 14 Sep 2014 13:54:21 +0000 Message-ID: References: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: x-originating-ip: [10.60.114.231] Content-Type: multipart/signed; boundary="Apple-Mail=_7527CF8A-FD21-4806-BF60-A72DD3E20F1C"; protocol="application/pgp-signature"; micalg=pgp-sha512 MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/pce/zP9oJfKrED43y-tt9dqYQHxygUU Subject: [Pce] Fwd: Adopting of draft-sivabalan-pce-segment-routing-03.txt as PCE WG Document X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Sep 2014 13:54:24 -0000 --Apple-Mail=_7527CF8A-FD21-4806-BF60-A72DD3E20F1C Content-Type: multipart/alternative; boundary="Apple-Mail=_E57FEA9A-7558-4AC1-B772-8003FBB0935D" --Apple-Mail=_E57FEA9A-7558-4AC1-B772-8003FBB0935D Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Begin forwarded message: > From: "JP Vasseur (jvasseur)" > Subject: [Pce] Adopting of draft-sivabalan-pce-segment-routing-03.txt = as PCE WG Document > Date: September 14, 2014 at 12:06:28 PM GMT+2 > To: "pce@ietf.org" >=20 > Dear WG, >=20 > We had several discussions showing a good consensus adopting = draft-sivabalan-pce-segment-routing-03.txt and this work > has considerably progressed in other WG. >=20 > Are you in favor of adopting = draft-sivabalan-pce-segment-routing-03.txt as a PCE WG document ? >=20 > Thanks. >=20 > JP and Julien. >=20 >=20 >=20 > _______________________________________________ > Pce mailing list > Pce@ietf.org > https://www.ietf.org/mailman/listinfo/pce --Apple-Mail=_E57FEA9A-7558-4AC1-B772-8003FBB0935D Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii

Begin forwarded = message:

From: = "JP Vasseur = (jvasseur)" <jvasseur@cisco.com>
Subject: [Pce] Adopting of = draft-sivabalan-pce-segment-routing-03.txt as PCE WG = Document
Date: = September 14, 2014 = at 12:06:28 PM GMT+2

Dear WG,

We had several discussions showing a good consensus = adopting draft-sivabalan-pce-segment-routing-03.txt and this work
has = considerably progressed in other WG.

Are you in favor of adopting = draft-sivabalan-pce-segment-routing-03.txt as a PCE WG document = ?

Thanks.

JP and = Julien.



_______________________________________________
= Pce mailing list
Pce@ietf.org
https://www.ietf.org/mail= man/listinfo/pce

= --Apple-Mail=_E57FEA9A-7558-4AC1-B772-8003FBB0935D-- --Apple-Mail=_7527CF8A-FD21-4806-BF60-A72DD3E20F1C Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="signature.asc" Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQEcBAEBCgAGBQJUFZ4FAAoJEHBVWzpLl1Mt65IH/3srvugR6SoKqnI9g68ILr+m Mq7NAKAKqlXkVEFzxo3djBxyEhCiPgP/Cq3fl9mM4bhR0U9e+fyUVuExeqxt1TFo ZejWWqXw9fSkNvlLM435itpo35X2U4r04eRicIMdV3CqSYz5RhtbY7scu0XTQ+cg p1YAH/fEg3YoWLU86nc7qUXmYGbGAc1lQkhrH+2W3+2F7tE/ddtrUgfrHYZ7/G7J LEz3Md5JKwXFndVF8QIujyv9XVr1nmmGufI3TaM2T2+VORfyDbcENUcpdlSrPRlf Lsf0Glnh+7VpwJ3MXpln72wY/LQedbVHrdlja5y0EVaqql9XDEZ8WOJuJICmLkI= =9zPI -----END PGP SIGNATURE----- --Apple-Mail=_7527CF8A-FD21-4806-BF60-A72DD3E20F1C-- From nobody Sun Sep 14 12:20:01 2014 Return-Path: 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 DB18D1A0196 for ; Sun, 14 Sep 2014 12:19:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -16.152 X-Spam-Level: X-Spam-Status: No, score=-16.152 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.652, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 uqmV8dcG2ZD0 for ; Sun, 14 Sep 2014 12:19:58 -0700 (PDT) Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D82561A0193 for ; Sun, 14 Sep 2014 12:19:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7332; q=dns/txt; s=iport; t=1410722399; x=1411931999; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=+lMbbZSnmRJW7H69j3CXQ1Xqto9g94+U43wUw0TkQng=; b=fW/m8baJ1LOiyZE0D7xIZ9bCOZ13LJ8JgOU5Z3eUGakv6p7qgxdxO2tS 2B6VYRNGQedzVaLGcc+iS6+eX7UjXKX+HKve5yTIXFlywTSnlqyvdhA8J fAx1UXk3w49o31rOHkGE5yt2rqE/UzF97ltRqdF3jSK/yIpQ9j7gui5bd 0=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AjMFAAbqFVStJV2U/2dsb2JhbABggkdGU1cEyUkBCYdOAYEGFniEAwEBAQQBAQEqQQsQAgEIEQMBAQELHQcnCxQJCAIEAQ0FCIg2DbhZARMEjxwgDQQGAQaDKIEdBY83ghageoIbgUNsgUiBAgEBAQ X-IronPort-AV: E=Sophos; i="5.04,522,1406592000"; d="scan'208,217"; a="77839566" Received: from rcdn-core-12.cisco.com ([173.37.93.148]) by alln-iport-5.cisco.com with ESMTP; 14 Sep 2014 19:19:58 +0000 Received: from xhc-aln-x02.cisco.com (xhc-aln-x02.cisco.com [173.36.12.76]) by rcdn-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id s8EJJuMA017193 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for ; Sun, 14 Sep 2014 19:19:56 GMT Received: from xmb-aln-x09.cisco.com ([169.254.4.28]) by xhc-aln-x02.cisco.com ([173.36.12.76]) with mapi id 14.03.0195.001; Sun, 14 Sep 2014 14:19:56 -0500 From: "Santiago Alvarez (saalvare)" To: "JP Vasseur (jvasseur)" , "pce@ietf.org" Thread-Topic: [Pce] Fwd: Adopting of draft-sivabalan-pce-segment-routing-03.txt as PCE WG Document Thread-Index: AQHP0AOM1KLRLywSpUW4vDYHaosXcpwBAZJw Date: Sun, 14 Sep 2014 19:19:55 +0000 Message-ID: <0C8935EE66D53445A3D3982BD9BE546821EAF96C@xmb-aln-x09.cisco.com> References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.82.208.216] Content-Type: multipart/alternative; boundary="_000_0C8935EE66D53445A3D3982BD9BE546821EAF96Cxmbalnx09ciscoc_" MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/pce/2CCtm-b6YaON5sAa587QqQHaV-E Subject: Re: [Pce] Fwd: Adopting of draft-sivabalan-pce-segment-routing-03.txt as PCE WG Document X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Sep 2014 19:20:00 -0000 --_000_0C8935EE66D53445A3D3982BD9BE546821EAF96Cxmbalnx09ciscoc_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Support. SA -- From: Pce [mailto:pce-bounces@ietf.org] On Behalf Of JP Vasseur (jvasseur) Sent: Sunday, September 14, 2014 6:54 AM To: pce@ietf.org Subject: [Pce] Fwd: Adopting of draft-sivabalan-pce-segment-routing-03.txt = as PCE WG Document Begin forwarded message: From: "JP Vasseur (jvasseur)" > Subject: [Pce] Adopting of draft-sivabalan-pce-segment-routing-03.txt as PC= E WG Document Date: September 14, 2014 at 12:06:28 PM GMT+2 To: "pce@ietf.org" > Dear WG, We had several discussions showing a good consensus adopting draft-sivabala= n-pce-segment-routing-03.txt and this work has considerably progressed in other WG. Are you in favor of adopting draft-sivabalan-pce-segment-routing-03.txt as = a PCE WG document ? Thanks. JP and Julien. _______________________________________________ Pce mailing list Pce@ietf.org https://www.ietf.org/mailman/listinfo/pce --_000_0C8935EE66D53445A3D3982BD9BE546821EAF96Cxmbalnx09ciscoc_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Support.

 <= /p>

SA

--

 <= /p>

From: Pce [mai= lto:pce-bounces@ietf.org] On Behalf Of JP Vasseur (jvasseur)
Sent: Sunday, September 14, 2014 6:54 AM
To: pce@ietf.org
Subject: [Pce] Fwd: Adopting of draft-sivabalan-pce-segment-routing-= 03.txt as PCE WG Document

 

 

 

Begin forwarded message:



From: "JP Vasseur (jvasseur)" <jvasseur@cisco.com>

Subject: [Pce] Adopting of draft-sivabalan-pce-segm= ent-routing-03.txt as PCE WG Document

Date: September 14, 2014 at 12:06:28 PM GMT+2

 

Dear WG,

We had several discussions showing a good consensus adopting draft-sivabala= n-pce-segment-routing-03.txt and this work
has considerably progressed in other WG.

Are you in favor of adopting draft-sivabalan-pce-segment-routing-03.txt as = a PCE WG document ?

Thanks.

JP and Julien.



_______________________________________________
Pce mailing list
Pce@ietf.org
https://www.ietf.org/= mailman/listinfo/pce

 

--_000_0C8935EE66D53445A3D3982BD9BE546821EAF96Cxmbalnx09ciscoc_-- From nobody Sun Sep 14 14:30:35 2014 Return-Path: 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 E36A41A02D8 for ; Sun, 14 Sep 2014 14:30:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.601 X-Spam-Level: X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 yUDwx4heQcJv for ; Sun, 14 Sep 2014 14:30:32 -0700 (PDT) Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 882741A02C1 for ; Sun, 14 Sep 2014 14:30:32 -0700 (PDT) X-AuditID: c6180641-f79916d00000623a-97-5415b0d24bb8 Received: from EUSAAHC007.ericsson.se (Unknown_Domain [147.117.188.93]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id D9.BF.25146.2D0B5145; Sun, 14 Sep 2014 17:14:26 +0200 (CEST) Received: from EUSAAMB109.ericsson.se ([147.117.188.126]) by EUSAAHC007.ericsson.se ([147.117.188.93]) with mapi id 14.03.0174.001; Sun, 14 Sep 2014 17:30:24 -0400 From: Jeff Tantsura To: "JP Vasseur (jvasseur)" Thread-Topic: [Pce] Adopting of draft-sivabalan-pce-segment-routing-03.txt as PCE WG Document Thread-Index: AQHP0GMY65c4mZeFRUGOQMzdpLpEXQ== Date: Sun, 14 Sep 2014 21:30:24 +0000 Message-ID: <06F2ED7B-B12F-4C2F-AEAB-115FEC929060@ericsson.com> References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrMLMWRmVeSWpSXmKPExsUyuXRPrO6lDaIhBv0zpCxmbHnLbNF0/wa7 A5PHlN8bWT2WLPnJFMAUxWWTkpqTWZZapG+XwJXxctl35oI/LBWTft9gaWBsY+li5OSQEDCR mLbhMBOELSZx4d56NhBbSOAoo0TPBIEuRi4gezmjxMpv/xlBEmwCBhL/vx0HaxYBsluvTmMF sZkFFCW2H1gDViMsECdxfdEPNoiaeImt1/cyQth6EpcmrwTq5eBgEVCVuDI3BiTMK2AvsfLp HEaIvTYSW+/OBruHU8BW4s/jB2A2I9Bt30+tYYJYJS5x68l8qJsFJJbsOc8MYYtKvHz8D+oc HYkFuz+xQdjaEssWvmaG2CUocXLmE5YJjKKzkIyahaRlFpKWWUhaFjCyrGLkKC1OLctNNzLc xAiMhWMSbI47GBd8sjzEKMDBqMTDq7BUOESINbGsuDL3EKM0B4uSOK9m9bxgIYH0xJLU7NTU gtSi+KLSnNTiQ4xMHJxSDYymPpkKLFKHJ10/lOstb/tlUS2bUSOLs3YVh/rmjaKqHk1LPN8s KX185/tNlW0KUa9jFa2CFlvrch1IcX+oovJ1Fd9aw0kWZ7wP2ufqG59xsJs694RzvsiGtYuX FPkua3TWXbKd42hDld36D6qiX88tqbd5tM+4+5j50o5tgSFOXZcvsJjcd1FiKc5INNRiLipO BADtElhRZgIAAA== Archived-At: http://mailarchive.ietf.org/arch/msg/pce/94vElXdjBPEPbNEqZQWStQC-2Hk Cc: "pce@ietf.org" Subject: Re: [Pce] Adopting of draft-sivabalan-pce-segment-routing-03.txt as PCE WG Document X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Sep 2014 21:30:34 -0000 Hi, Support as co-author. Thanks! Regards, Jeff > On Sep 14, 2014, at 3:07 AM, "JP Vasseur (jvasseur)" = wrote: >=20 > Dear WG, >=20 > We had several discussions showing a good consensus adopting draft-sivaba= lan-pce-segment-routing-03.txt and this work > has considerably progressed in other WG. >=20 > Are you in favor of adopting draft-sivabalan-pce-segment-routing-03.txt a= s a PCE WG document ? >=20 > Thanks. >=20 > JP and Julien. >=20 >=20 >=20 > _______________________________________________ > Pce mailing list > Pce@ietf.org > https://www.ietf.org/mailman/listinfo/pce From nobody Sun Sep 14 15:54:38 2014 Return-Path: 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 0316C1A03D0 for ; Sun, 14 Sep 2014 15:54:37 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -16.153 X-Spam-Level: X-Spam-Status: No, score=-16.153 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.652, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 tNVU2HUpSiTT for ; Sun, 14 Sep 2014 15:54:35 -0700 (PDT) Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7DA2C1A03E1 for ; Sun, 14 Sep 2014 15:54:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=896; q=dns/txt; s=iport; t=1410735275; x=1411944875; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=vxEXTjK+UueNLYw2lb7wtOwNY1kK6p87+kXzZXBJ4oY=; b=ffdAzYZm88qGkIR+Mm/9AJmNmZM/cypqh3Axz9lXFu++tO2vwxe3qoVy ZDlAoYWo0hD9Y11vPZU21Cmnk8QjkkQQnrTY2j0JiUbfMcFSFCWea28Cf F0jlsK/lhI3i7dYs5xSmYqn08+Ff/dwg1W8Lr10VxXiJ8B3/SGh6RESMn 0=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AhwFAGQbFlStJA2D/2dsb2JhbABggw1TVwTJTAqHTgGBCBZ4hAQBAQQBAQE3NAsQAgEIGB4QJwslAgQBDQWIPg24fQETBI9NB4RLAQSRTYs7lT+CG4FDbIFIgQIBAQE X-IronPort-AV: E=Sophos;i="5.04,523,1406592000"; d="scan'208";a="77858400" Received: from alln-core-1.cisco.com ([173.36.13.131]) by alln-iport-5.cisco.com with ESMTP; 14 Sep 2014 22:54:34 +0000 Received: from xhc-rcd-x15.cisco.com (xhc-rcd-x15.cisco.com [173.37.183.89]) by alln-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s8EMsYBS027030 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sun, 14 Sep 2014 22:54:34 GMT Received: from xmb-aln-x10.cisco.com ([169.254.5.49]) by xhc-rcd-x15.cisco.com ([173.37.183.89]) with mapi id 14.03.0195.001; Sun, 14 Sep 2014 17:54:34 -0500 From: "Jan Medved (jmedved)" To: Jeff Tantsura , "JP Vasseur (jvasseur)" Thread-Topic: [Pce] Adopting of draft-sivabalan-pce-segment-routing-03.txt as PCE WG Document Thread-Index: AQHP0AOM1KLRLywSpUW4vDYHaosXcpwBefoA//+iKwA= Date: Sun, 14 Sep 2014 22:54:34 +0000 Message-ID: References: <06F2ED7B-B12F-4C2F-AEAB-115FEC929060@ericsson.com> In-Reply-To: <06F2ED7B-B12F-4C2F-AEAB-115FEC929060@ericsson.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.4.4.140807 x-originating-ip: [10.27.7.167] Content-Type: text/plain; charset="us-ascii" Content-ID: <46AAE786B84699478CC1317EBC5EAA90@emea.cisco.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/pce/z6bvTNxiu42Mz-vHX4vDkdrDWsc Cc: "pce@ietf.org" Subject: Re: [Pce] Adopting of draft-sivabalan-pce-segment-routing-03.txt as PCE WG Document X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Sep 2014 22:54:37 -0000 Support as a co-author On 9/14/14, 2:30 PM, "Jeff Tantsura" wrote: >Hi, > >Support as co-author. >Thanks! > >Regards, >Jeff > >> On Sep 14, 2014, at 3:07 AM, "JP Vasseur (jvasseur)" >> wrote: >>=20 >> Dear WG, >>=20 >> We had several discussions showing a good consensus adopting >>draft-sivabalan-pce-segment-routing-03.txt and this work >> has considerably progressed in other WG. >>=20 >> Are you in favor of adopting draft-sivabalan-pce-segment-routing-03.txt >>as a PCE WG document ? >>=20 >> Thanks. >>=20 >> JP and Julien. >>=20 >>=20 >>=20 >> _______________________________________________ >> 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 From nobody Sun Sep 14 15:55:01 2014 Return-Path: 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 2D5E81A03E1 for ; Sun, 14 Sep 2014 15:55:01 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.601 X-Spam-Level: X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 fl8TbXTlMuKh for ; Sun, 14 Sep 2014 15:55:00 -0700 (PDT) Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EC4B31A03D0 for ; Sun, 14 Sep 2014 15:54:59 -0700 (PDT) X-AuditID: c6180641-f79916d00000623a-11-5415c4a2bbec Received: from EUSAAHC002.ericsson.se (Unknown_Domain [147.117.188.78]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id EB.50.25146.2A4C5145; Sun, 14 Sep 2014 18:38:58 +0200 (CEST) Received: from EUSAAMB103.ericsson.se ([147.117.188.120]) by EUSAAHC002.ericsson.se ([147.117.188.78]) with mapi id 14.03.0174.001; Sun, 14 Sep 2014 18:54:57 -0400 From: Autumn Liu To: "JP Vasseur (jvasseur)" , "pce@ietf.org" Thread-Topic: Adopting of draft-sivabalan-pce-segment-routing-03.txt as PCE WG Document Thread-Index: AQHP0AOM1KLRLywSpUW4vDYHaosXcpwBPYlQ Date: Sun, 14 Sep 2014 22:54:57 +0000 Message-ID: References: In-Reply-To: Accept-Language: zh-CN, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [147.117.188.9] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrCLMWRmVeSWpSXmKPExsUyuXSPn+6iI6IhBo3rFC1mbHnLbNF0/wa7 A5PHlN8bWT2WLPnJFMAUxWWTkpqTWZZapG+XwJWxeOV9xoJLLBX3V/9namB8ztzFyMkhIWAi sfhsM5QtJnHh3nq2LkYuDiGBo4wSU89vZoVwljNKLOtayQ5SxSagJbFv/zsgm4NDRCBQovF5 AkhYWCBC4uz9KWwgtohApMSH9btYIGwjiY+Pr4K1sgioSny/0sAIYvMK+Eq0fL/MBGILCdhI bL07G8zmFLCV+PP4AZjNKCArMe3RfTCbWUBc4taT+UwQhwpILNlzHupoUYmXj/+xQtiKEvv6 p7ND1OtILNj9iQ3C1pZYtvA1M8ReQYmTM5+wTGAUnYVk7CwkLbOQtMxC0rKAkWUVI0dpcWpZ brqR4SZGYDQck2Bz3MG44JPlIUYBDkYlHl6FpcIhQqyJZcWVuYcYpTlYlMR5NavnBQsJpCeW pGanphakFsUXleakFh9iZOLglGpgPFJu0//1QPicx0vTPpZoRAfovXLtdb6hsHTtKvtXyYan 0vm+PGsLsIjU+aNnoeSupdxh/JZb8Jym6OIHi7oZU+azWPuveD/vbcfdM64nrG5cWrlIyDF+ yjuexXNLd58IEIw8luPBeyHx3NE30z/4LTz5Ql6kre+OoEL9goXeHkIOsac8z90tVWIpzkg0 1GIuKk4EAHMPSXNnAgAA Archived-At: http://mailarchive.ietf.org/arch/msg/pce/smzUu0qLFEuLdLO0du6o4WbCGko Subject: Re: [Pce] Adopting of draft-sivabalan-pce-segment-routing-03.txt as PCE WG Document X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Sep 2014 22:55:01 -0000 Support. -Autumn -----Original Message----- From: Pce [mailto:pce-bounces@ietf.org] On Behalf Of JP Vasseur (jvasseur) Sent: Sunday, September 14, 2014 3:06 AM To: pce@ietf.org Subject: [Pce] Adopting of draft-sivabalan-pce-segment-routing-03.txt as PC= E WG Document Dear WG, We had several discussions showing a good consensus adopting draft-sivabala= n-pce-segment-routing-03.txt and this work has considerably progressed in o= ther WG. Are you in favor of adopting draft-sivabalan-pce-segment-routing-03.txt as = a PCE WG document ? Thanks. JP and Julien. From nobody Sun Sep 14 16:59:59 2014 Return-Path: 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 E51EF1A0422 for ; Sun, 14 Sep 2014 16:59:56 -0700 (PDT) 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, 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 b4ZNEITjP8kc for ; Sun, 14 Sep 2014 16:59:55 -0700 (PDT) Received: from mail-vc0-x236.google.com (mail-vc0-x236.google.com [IPv6:2607:f8b0:400c:c03::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 91B8F1A0426 for ; Sun, 14 Sep 2014 16:59:54 -0700 (PDT) Received: by mail-vc0-f182.google.com with SMTP id le20so2796816vcb.13 for ; Sun, 14 Sep 2014 16:59:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=ZogS3dv0nI0vM1hZErlPlctnI93XFMNQIwujXFRMLbI=; b=Rx3MGT44MQ6g41hZGIf0Bn9ROusG0i7Gseb2qGXLX8ZCKdqPuHM3xFagFnusbBDrwy s53a6SYD8mvnQfnJ/rRuR97DPjWSiMLJypHH05xkJS56iVg1TozVEszsY2jhveZeikTT M+kZMXv4G8QcaoVIJ7HHm0leJyduOxHseLsFIEjBrE76S+9yS6buZOLYJ+QcIPWHDz2a Qp2EUVkX7/eJd7GAT46DO4H4iXh476Yd7kzp/GhlRNN40yC6sUHDwVqEUTAiMZgt94LC +qo0+vXv3my173lG0gKl+SfNzutoj8Jn2S8QGcotxl3fCboumkGY0RGWTn1zH+hsUH/x cxJA== MIME-Version: 1.0 X-Received: by 10.220.2.133 with SMTP id 5mr11151873vcj.48.1410739193627; Sun, 14 Sep 2014 16:59:53 -0700 (PDT) Received: by 10.220.43.208 with HTTP; Sun, 14 Sep 2014 16:59:53 -0700 (PDT) In-Reply-To: References: Date: Mon, 15 Sep 2014 01:59:53 +0200 Message-ID: From: Greg Mirsky To: "JP Vasseur (jvasseur)" Content-Type: multipart/alternative; boundary=001a11c3dbe481c86e05030f505d Archived-At: http://mailarchive.ietf.org/arch/msg/pce/QdRnHulT1SYN1MBBx6fHtNysUqA Cc: "pce@ietf.org" Subject: Re: [Pce] Adopting of draft-sivabalan-pce-segment-routing-03.txt as PCE WG Document X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Sep 2014 23:59:57 -0000 --001a11c3dbe481c86e05030f505d Content-Type: text/plain; charset=UTF-8 Support Regards, Greg On Sun, Sep 14, 2014 at 12:06 PM, JP Vasseur (jvasseur) wrote: > Dear WG, > > We had several discussions showing a good consensus adopting > draft-sivabalan-pce-segment-routing-03.txt and this work > has considerably progressed in other WG. > > Are you in favor of adopting draft-sivabalan-pce-segment-routing-03.txt as > a PCE WG document ? > > Thanks. > > JP and Julien. > > > > > _______________________________________________ > Pce mailing list > Pce@ietf.org > https://www.ietf.org/mailman/listinfo/pce > > --001a11c3dbe481c86e05030f505d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Support

Regards,
Greg
<= /div>

On Sun, Sep = 14, 2014 at 12:06 PM, JP Vasseur (jvasseur) <jvasseur@cisco.com>= wrote:
Dear WG,

We had several discussions showing a good consensus adopting draft-sivabala= n-pce-segment-routing-03.txt and this work
has considerably progressed in other WG.

Are you in favor of adopting draft-sivabalan-pce-segment-routing-03.txt as = a PCE WG document ?

Thanks.

JP and Julien.




_______________________________________________
Pce mailing list
Pce@ietf.org
htt= ps://www.ietf.org/mailman/listinfo/pce


--001a11c3dbe481c86e05030f505d-- From nobody Sun Sep 14 17:01:28 2014 Return-Path: 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 BA1BB1A0426 for ; Sun, 14 Sep 2014 17:01:26 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.267 X-Spam-Level: X-Spam-Status: No, score=-2.267 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_LOW=-0.7, 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 QERyrZZacoZh for ; Sun, 14 Sep 2014 17:01:25 -0700 (PDT) Received: from mx0b-00103a01.pphosted.com (mx0b-00103a01.pphosted.com [67.231.152.227]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4EFE31A0422 for ; Sun, 14 Sep 2014 17:01:25 -0700 (PDT) Received: from pps.filterd (m0002317.ppops.net [127.0.0.1]) by mx0b-00103a01.pphosted.com (8.14.5/8.14.5) with SMTP id s8ENxNRb022615; Sun, 14 Sep 2014 20:01:23 -0400 Received: from mdwexght02.ciena.com (LIN1-118-36-29.ciena.com [63.118.36.29]) by mx0b-00103a01.pphosted.com with ESMTP id 1pc73xkmww-1 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Sun, 14 Sep 2014 20:01:23 -0400 Received: from VAWVE2K13MBX01.ciena.com (10.4.156.87) by MDWEXGHT02.ciena.com (10.4.140.213) with Microsoft SMTP Server (TLS) id 8.3.298.1; Sun, 14 Sep 2014 20:01:22 -0400 Received: from ONWVEXCHHT03.ciena.com (10.128.6.43) by VAWVE2K13MBX01.ciena.com (10.4.156.87) with Microsoft SMTP Server (TLS) id 15.0.847.32; Sun, 14 Sep 2014 20:01:22 -0400 Received: from ONWVEXCHMB04.ciena.com ([::1]) by ONWVEXCHHT03.ciena.com ([::1]) with mapi; Sun, 14 Sep 2014 20:01:22 -0400 From: "Shah, Himanshu" To: "JP Vasseur (jvasseur)" , "pce@ietf.org" Date: Sun, 14 Sep 2014 20:00:37 -0400 Thread-Topic: [Pce] Fwd: Adopting of draft-sivabalan-pce-segment-routing-03.txt as PCE WG Document Thread-Index: AQHP0CNiCCtRNqCSWEqUClZSmzJWKZwBT+IS Message-ID: <40746B2300A8FC4AB04EE722A593182B78AC1909@ONWVEXCHMB04.ciena.com> References: , In-Reply-To: Accept-Language: en-US, en-CA Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, en-CA X-TM-AS-Product-Ver: SMEX-10.0.0.1412-7.000.1014-20952.003 X-TM-AS-Result: No--17.544800-0.000000-31 X-TM-AS-User-Approved-Sender: Yes X-TM-AS-User-Blocked-Sender: No Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.12.52, 1.0.28, 0.0.0000 definitions=2014-09-14_03:2014-09-12,2014-09-14,1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1402240000 definitions=main-1409140253 Archived-At: http://mailarchive.ietf.org/arch/msg/pce/zqIKRPPXLS4drDUEOIYj5RN8JkY Subject: Re: [Pce] Fwd: Adopting of draft-sivabalan-pce-segment-routing-03.txt as PCE WG Document X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Sep 2014 00:01:26 -0000 Support /himanshu ________________________________________ From: Pce [pce-bounces@ietf.org] On Behalf Of JP Vasseur (jvasseur) [jvasse= ur@cisco.com] Sent: Sunday, September 14, 2014 9:54 AM To: pce@ietf.org Subject: [Pce] Fwd: Adopting of draft-sivabalan-pce-segment-routing-03.txt = as PCE WG Document Begin forwarded message: From: "JP Vasseur (jvasseur)" > Subject: [Pce] Adopting of draft-sivabalan-pce-segment-routing-03.txt as PC= E WG Document Date: September 14, 2014 at 12:06:28 PM GMT+2 To: "pce@ietf.org" > Dear WG, We had several discussions showing a good consensus adopting draft-sivabala= n-pce-segment-routing-03.txt and this work has considerably progressed in other WG. Are you in favor of adopting draft-sivabalan-pce-segment-routing-03.txt as = a PCE WG document ? Thanks. JP and Julien. _______________________________________________ Pce mailing list Pce@ietf.org https://www.ietf.org/mailman/listinfo/pce From nobody Sun Sep 14 18:40:23 2014 Return-Path: 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 91C401A0481 for ; Sun, 14 Sep 2014 18:40:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.853 X-Spam-Level: X-Spam-Status: No, score=-5.853 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-1.652, 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 amDsIPDRvz4g for ; Sun, 14 Sep 2014 18:40:21 -0700 (PDT) Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5D8CA1A047E for ; Sun, 14 Sep 2014 18:40:21 -0700 (PDT) Received: from 172.18.7.190 (EHLO lhreml402-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BJK28562; Mon, 15 Sep 2014 01:40:20 +0000 (GMT) Received: from nkgeml407-hub.china.huawei.com (10.98.56.38) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 15 Sep 2014 02:40:19 +0100 Received: from NKGEML512-MBS.china.huawei.com ([169.254.8.18]) by nkgeml407-hub.china.huawei.com ([10.98.56.38]) with mapi id 14.03.0158.001; Mon, 15 Sep 2014 09:40:14 +0800 From: Xuxiaohu To: "JP Vasseur (jvasseur)" , "pce@ietf.org" Thread-Topic: Adopting of draft-sivabalan-pce-segment-routing-03.txt as PCE WG Document Thread-Index: AQHP0AOM1KLRLywSpUW4vDYHaosXcpwBa98A Date: Mon, 15 Sep 2014 01:40:13 +0000 Message-ID: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE082B576A@NKGEML512-MBS.china.huawei.com> References: In-Reply-To: Accept-Language: zh-CN, en-US Content-Language: zh-CN X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.111.98.134] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-CFilter-Loop: Reflected Archived-At: http://mailarchive.ietf.org/arch/msg/pce/30a65o7ipbO-kS2Vs-KLXfjVW3U Subject: Re: [Pce] Adopting of draft-sivabalan-pce-segment-routing-03.txt as PCE WG Document X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Sep 2014 01:40:22 -0000 Support. Xiaohu -----Original Message----- From: Pce [mailto:pce-bounces@ietf.org] On Behalf Of JP Vasseur (jvasseur) Sent: Sunday, September 14, 2014 6:06 PM To: pce@ietf.org Subject: [Pce] Adopting of draft-sivabalan-pce-segment-routing-03.txt as PC= E WG Document Dear WG, We had several discussions showing a good consensus adopting draft-sivabala= n-pce-segment-routing-03.txt and this work has considerably progressed in o= ther WG. Are you in favor of adopting draft-sivabalan-pce-segment-routing-03.txt as = a PCE WG document ? Thanks. JP and Julien. From nobody Sun Sep 14 21:18:02 2014 Return-Path: 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 32D6E1A0639 for ; Sun, 14 Sep 2014 21:18:01 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -16.153 X-Spam-Level: X-Spam-Status: No, score=-16.153 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.652, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 YM3UhllD7d_i for ; Sun, 14 Sep 2014 21:18:00 -0700 (PDT) Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 140BC1A0572 for ; Sun, 14 Sep 2014 21:18:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=612; q=dns/txt; s=iport; t=1410754680; x=1411964280; h=from:to:subject:date:message-id:in-reply-to:content-id: content-transfer-encoding:mime-version; bh=0KXnVbUFs1YP2T46RXfnqQv+gxZvjzoOzd4f37t+Dkk=; b=YP7YGzLuEWVx46bx/o5hWghMVO88N/IdI4slXFKGtbtGFgK1kVhoHul0 3AvvhnSwfc4dDD8ly3XIHifwikJmbAVsDo9Hs9DECNmf/NvPaScPz591D ranmhiQXhQpAYNsGP9YbspDTIORu+dv6Z+0Lr1Pd2DYB6zATGQDqzLM2/ U=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AhgFACRoFlStJV2Y/2dsb2JhbABfgw2BKgTRdwGBDxZ4hAMBAQEEgQUGAQgRAwECYR0IAgQBEog+uV0BF49UBoRFAQSPN4IWizuVP4IbgUNsgUiBAgEBAQ X-IronPort-AV: E=Sophos;i="5.04,525,1406592000"; d="scan'208";a="355210542" Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-8.cisco.com with ESMTP; 15 Sep 2014 04:17:57 +0000 Received: from xhc-rcd-x13.cisco.com (xhc-rcd-x13.cisco.com [173.37.183.87]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s8F4HvaM027596 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for ; Mon, 15 Sep 2014 04:17:57 GMT Received: from xmb-rcd-x14.cisco.com ([169.254.4.204]) by xhc-rcd-x13.cisco.com ([173.37.183.87]) with mapi id 14.03.0195.001; Sun, 14 Sep 2014 23:17:57 -0500 From: "Zafar Ali (zali)" To: "JP Vasseur (jvasseur)" , "pce@ietf.org" Thread-Topic: [Pce] Adoption of draft-sivabalan-pce-lsp-setup-type-02.txt as a PCE WG Document Thread-Index: AQHP0AOKhQXX3FptfUeVYEz+5mQyKZwBq0KA Date: Mon, 15 Sep 2014 04:17:57 +0000 Message-ID: In-Reply-To: <70E9F53F-3A40-4CC6-924B-9BA229FD84AA@cisco.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.2.3.120616 x-originating-ip: [10.86.244.47] Content-Type: text/plain; charset="Windows-1252" Content-ID: <445DEDFD3BAE004E8F299836F6F674FE@emea.cisco.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/pce/QR-UpQOtPaL_dXuu_IBdbMwpOmM Subject: Re: [Pce] Adoption of draft-sivabalan-pce-lsp-setup-type-02.txt as a PCE WG Document X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Sep 2014 04:18:01 -0000 Support! Thanks Regards =8A Zafar -----Original Message----- From: "JP Vasseur (jvasseur)" Date: Sunday, September 14, 2014 6:06 AM To: "pce@ietf.org" Subject: [Pce] Adoption of draft-sivabalan-pce-lsp-setup-type-02.txt as a PCE WG Document >Dear WG, > >We had several discussions showing a good consensus adopting >draft-sivabalan-pce-lsp-setup-type-02.txt and this work >has considerably progressed in other WG. > >Are you in favor of adopting draft-sivabalan-pce-lsp-setup-type-02.txt as >a PCE WG document ? > >Thanks. > >JP and Julien. From nobody Sun Sep 14 21:18:20 2014 Return-Path: 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 149B31A063C for ; Sun, 14 Sep 2014 21:18:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -16.153 X-Spam-Level: X-Spam-Status: No, score=-16.153 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.652, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 gx4k34-GQJ_S for ; Sun, 14 Sep 2014 21:18:18 -0700 (PDT) Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 08EFE1A0639 for ; Sun, 14 Sep 2014 21:18:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=626; q=dns/txt; s=iport; t=1410754698; x=1411964298; h=from:to:subject:date:message-id:in-reply-to:content-id: content-transfer-encoding:mime-version; bh=Fz+yPPyB3m4W+zEkrT5kNd6Gg6YGRrUBZaC9+Gby6fM=; b=Hn4PH34nxDJASLmCFdwu4q56ehaTU/1Tjoar2J0ld/yGCCC8QYg7k51s 9dU4FUGEnGCGjWvD3md/CCFeVXopjra6NJ2P/l2Uy7rp9VsFpoIT23S77 HC8E1u4B5XYMoVe31jXVskCD45GUq7vQKS/99wbyi5ofdJzeJylOdpc9T M=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AhgFADVnFlStJA2J/2dsb2JhbABfgw2BKgTRdAGBDxZ4hAMBAQEEgQUGAQgRAwECYR0IAgQBEog+uVwBF49UBoRFAQSPN4IWizuVP4IbgUNsgUiBAgEBAQ X-IronPort-AV: E=Sophos;i="5.04,525,1406592000"; d="scan'208";a="77897479" Received: from alln-core-4.cisco.com ([173.36.13.137]) by alln-iport-7.cisco.com with ESMTP; 15 Sep 2014 04:18:17 +0000 Received: from xhc-rcd-x03.cisco.com (xhc-rcd-x03.cisco.com [173.37.183.77]) by alln-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s8F4IHOg027902 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for ; Mon, 15 Sep 2014 04:18:17 GMT Received: from xmb-rcd-x14.cisco.com ([169.254.4.204]) by xhc-rcd-x03.cisco.com ([173.37.183.77]) with mapi id 14.03.0195.001; Sun, 14 Sep 2014 23:18:16 -0500 From: "Zafar Ali (zali)" To: "JP Vasseur (jvasseur)" , "pce@ietf.org" Thread-Topic: [Pce] Adopting of draft-sivabalan-pce-segment-routing-03.txt as PCE WG Document Thread-Index: AQHP0AOM1KLRLywSpUW4vDYHaosXcpwBq1kA Date: Mon, 15 Sep 2014 04:18:16 +0000 Message-ID: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.2.3.120616 x-originating-ip: [10.86.244.47] Content-Type: text/plain; charset="Windows-1252" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/pce/ZfXL8tSpCrl1UnjXvcNVyhJn4jg Subject: Re: [Pce] Adopting of draft-sivabalan-pce-segment-routing-03.txt as PCE WG Document X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Sep 2014 04:18:19 -0000 Support! Thanks Regards =8A Zafar -----Original Message----- From: "JP Vasseur (jvasseur)" Date: Sunday, September 14, 2014 6:06 AM To: "pce@ietf.org" Subject: [Pce] Adopting of draft-sivabalan-pce-segment-routing-03.txt as PCE WG Document >Dear WG, > >We had several discussions showing a good consensus adopting >draft-sivabalan-pce-segment-routing-03.txt and this work >has considerably progressed in other WG. > >Are you in favor of adopting draft-sivabalan-pce-segment-routing-03.txt >as a PCE WG document ? > >Thanks. > >JP and Julien. > > > From nobody Sun Sep 14 21:48:12 2014 Return-Path: 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 692A11A0645 for ; Sun, 14 Sep 2014 21:48:10 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.064 X-Spam-Level: X-Spam-Status: No, score=-3.064 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CN_BODY_35=0.339, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-1.652, 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 lI6ywDGNYDRj for ; Sun, 14 Sep 2014 21:48:08 -0700 (PDT) Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B8EC81A0643 for ; Sun, 14 Sep 2014 21:48:07 -0700 (PDT) Received: from 172.18.7.190 (EHLO lhreml402-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BMO03081; Mon, 15 Sep 2014 04:48:05 +0000 (GMT) Received: from NKGEML402-HUB.china.huawei.com (10.98.56.33) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 15 Sep 2014 05:48:03 +0100 Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.21]) by nkgeml402-hub.china.huawei.com ([10.98.56.33]) with mapi id 14.03.0158.001; Mon, 15 Sep 2014 12:48:00 +0800 From: Qin Wu To: "pce@ietf.org" Thread-Topic: I-D Action: draft-wu-pce-traffic-steering-sfc-05.txt Thread-Index: AQHP0J+rVi7ruZxAiUyY91/Z5jkYapwBnirg Date: Mon, 15 Sep 2014 04:47:59 +0000 Message-ID: Accept-Language: zh-CN, en-US Content-Language: zh-CN X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.138.41.180] Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: base64 MIME-Version: 1.0 X-CFilter-Loop: Reflected Archived-At: http://mailarchive.ietf.org/arch/msg/pce/9Hh7d82x46Kga82D_7F6TlOGtpU Subject: Re: [Pce] I-D Action: draft-wu-pce-traffic-steering-sfc-05.txt X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Sep 2014 04:48:10 -0000 SGk6DQpUbyBnZXQgY29uc2lzdGVudCB3aXRoIG5ld2x5IGFkb3B0ZWQgZHJhZnQtaWV0Zi1zZmMt YXJjaGl0ZWN0dXJlLCANCmhlcmUgaXMgdGhlIHVwZGF0ZSB0byBkcmFmdC13dS1wY2UtdHJhZmZp Yy1zdGVlcmluZy1zZmMgd2hpY2ggZGlzY3VzcyBQQ0VQIGV4dGVuc2lvbiBmb3IgU0ZDIHN1cHBv cnQuDQpUaGUgZGlmZiBpczoNCmh0dHA6Ly93d3cuaWV0Zi5vcmcvcmZjZGlmZj91cmwyPWRyYWZ0 LXd1LXBjZS10cmFmZmljLXN0ZWVyaW5nLXNmYy0wNQ0KDQpSZWdhcmRzIQ0KLVFpbg0KLS0tLS3T yrz+1K28/i0tLS0tDQq3orz+yMs6IEktRC1Bbm5vdW5jZSBbbWFpbHRvOmktZC1hbm5vdW5jZS1i b3VuY2VzQGlldGYub3JnXSC0+rHtIGludGVybmV0LWRyYWZ0c0BpZXRmLm9yZw0Kt6LLzcqxvOQ6 IDIwMTTE6jnUwjE1yNUgMTI6NDQNCsrVvP7IyzogaS1kLWFubm91bmNlQGlldGYub3JnDQrW98zi OiBJLUQgQWN0aW9uOiBkcmFmdC13dS1wY2UtdHJhZmZpYy1zdGVlcmluZy1zZmMtMDUudHh0DQoN Cg0KQSBOZXcgSW50ZXJuZXQtRHJhZnQgaXMgYXZhaWxhYmxlIGZyb20gdGhlIG9uLWxpbmUgSW50 ZXJuZXQtRHJhZnRzIGRpcmVjdG9yaWVzLg0KDQoNCiAgICAgICAgVGl0bGUgICAgICAgICAgIDog UENFUCBFeHRlbnNpb25zIGZvciB0cmFmZmljIHN0ZWVyaW5nIHN1cHBvcnQgaW4gU2VydmljZSBG dW5jdGlvbiBDaGFpbmluZw0KICAgICAgICBBdXRob3JzICAgICAgICAgOiBRaW4gV3UNCiAgICAg ICAgICAgICAgICAgICAgICAgICAgRGhydXYgRGhvZHkNCiAgICAgICAgICAgICAgICAgICAgICAg ICAgTW9oYW1lZCBCb3VjYWRhaXINCiAgICAgICAgICAgICAgICAgICAgICAgICAgQ2hyaXN0aWFu IEphY3F1ZW5ldA0KICAgICAgICAgICAgICAgICAgICAgICAgICBKZWZmIFRhbnRzdXJhDQoJRmls ZW5hbWUgICAgICAgIDogZHJhZnQtd3UtcGNlLXRyYWZmaWMtc3RlZXJpbmctc2ZjLTA1LnR4dA0K CVBhZ2VzICAgICAgICAgICA6IDEwDQoJRGF0ZSAgICAgICAgICAgIDogMjAxNC0wOS0xNA0KDQpB YnN0cmFjdDoNCiAgIFRoaXMgZG9jdW1lbnQgcHJvdmlkZXMgYW4gb3ZlcnZpZXcgb2YgdGhlIHVz YWdlIG9mIFBhdGggQ29tcHV0YXRpb24NCiAgIEVsZW1lbnQgKFBDRSkgd2l0aCBTZXJ2aWNlIEZ1 bmN0aW9uIENoYWluaW5nIChTRkMpOyB3aGljaCBpcw0KICAgZGVzY3JpYmVkIGFzIHRoZSBkZWZp bml0aW9uIGFuZCBpbnN0YW50aWF0aW9uIG9mIGFuIG9yZGVyZWQgc2V0IG9mDQogICBzdWNoIHNl cnZpY2UgZnVuY3Rpb25zIChzdWNoIGFzIGZpcmV3YWxscywgbG9hZCBiYWxhbmNlcnMpLCBhbmQg dGhlDQogICBzdWJzZXF1ZW50ICJzdGVlcmluZyIgb2YgdHJhZmZpYyBmbG93cyB0aHJvdWdoIHRo b3NlIHNlcnZpY2UNCiAgIGZ1bmN0aW9ucy4NCg0KICAgVGhpcyBkb2N1bWVudCBzcGVjaWZpZXMg ZXh0ZW5zaW9ucyB0byB0aGUgUGF0aCBDb21wdXRhdGlvbiBFbGVtZW50DQogICBQcm90b2NvbCAo UENFUCkgdGhhdCBhbGxvdyBhIHN0YXRlZnVsIFBDRSB0byBjb21wdXRlIGFuZCBpbnN0YW50aWF0 ZQ0KICAgU2VydmljZSBGdW5jdGlvbiBQYXRocyAoU0ZQKS4NCg0KDQpUaGUgSUVURiBkYXRhdHJh Y2tlciBzdGF0dXMgcGFnZSBmb3IgdGhpcyBkcmFmdCBpczoNCmh0dHBzOi8vZGF0YXRyYWNrZXIu aWV0Zi5vcmcvZG9jL2RyYWZ0LXd1LXBjZS10cmFmZmljLXN0ZWVyaW5nLXNmYy8NCg0KVGhlcmUn cyBhbHNvIGEgaHRtbGl6ZWQgdmVyc2lvbiBhdmFpbGFibGUgYXQ6DQpodHRwOi8vdG9vbHMuaWV0 Zi5vcmcvaHRtbC9kcmFmdC13dS1wY2UtdHJhZmZpYy1zdGVlcmluZy1zZmMtMDUNCg0KQSBkaWZm IGZyb20gdGhlIHByZXZpb3VzIHZlcnNpb24gaXMgYXZhaWxhYmxlIGF0Og0KaHR0cDovL3d3dy5p ZXRmLm9yZy9yZmNkaWZmP3VybDI9ZHJhZnQtd3UtcGNlLXRyYWZmaWMtc3RlZXJpbmctc2ZjLTA1 DQoNCg0KUGxlYXNlIG5vdGUgdGhhdCBpdCBtYXkgdGFrZSBhIGNvdXBsZSBvZiBtaW51dGVzIGZy b20gdGhlIHRpbWUgb2Ygc3VibWlzc2lvbiB1bnRpbCB0aGUgaHRtbGl6ZWQgdmVyc2lvbiBhbmQg ZGlmZiBhcmUgYXZhaWxhYmxlIGF0IHRvb2xzLmlldGYub3JnLg0KDQpJbnRlcm5ldC1EcmFmdHMg YXJlIGFsc28gYXZhaWxhYmxlIGJ5IGFub255bW91cyBGVFAgYXQ6DQpmdHA6Ly9mdHAuaWV0Zi5v cmcvaW50ZXJuZXQtZHJhZnRzLw0KDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fXw0KSS1ELUFubm91bmNlIG1haWxpbmcgbGlzdA0KSS1ELUFubm91bmNlQGll dGYub3JnDQpodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2ktZC1hbm5vdW5j ZQ0KSW50ZXJuZXQtRHJhZnQgZGlyZWN0b3JpZXM6IGh0dHA6Ly93d3cuaWV0Zi5vcmcvc2hhZG93 Lmh0bWwgb3IgZnRwOi8vZnRwLmlldGYub3JnL2lldGYvMXNoYWRvdy1zaXRlcy50eHQNCg== From nobody Sun Sep 14 21:48:57 2014 Return-Path: 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 D5C921A0643 for ; Sun, 14 Sep 2014 21:48:54 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.064 X-Spam-Level: X-Spam-Status: No, score=-3.064 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CN_BODY_35=0.339, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-1.652, 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 w_CI87__GukX for ; Sun, 14 Sep 2014 21:48:53 -0700 (PDT) Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 65E871A036F for ; Sun, 14 Sep 2014 21:48:53 -0700 (PDT) Received: from 172.18.7.190 (EHLO lhreml402-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BMO03126; Mon, 15 Sep 2014 04:48:52 +0000 (GMT) Received: from nkgeml409-hub.china.huawei.com (10.98.56.40) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 15 Sep 2014 05:48:51 +0100 Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.21]) by nkgeml409-hub.china.huawei.com ([10.98.56.40]) with mapi id 14.03.0158.001; Mon, 15 Sep 2014 12:48:47 +0800 From: Qin Wu To: "JP Vasseur (jvasseur)" , "pce@ietf.org" Thread-Topic: Adopting of draft-sivabalan-pce-segment-routing-03.txt as PCE WG Document Thread-Index: AQHP0AOM1KLRLywSpUW4vDYHaosXcpwBoIiw Date: Mon, 15 Sep 2014 04:48:46 +0000 Message-ID: References: In-Reply-To: Accept-Language: zh-CN, en-US Content-Language: zh-CN X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.138.41.180] Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: base64 MIME-Version: 1.0 X-CFilter-Loop: Reflected Archived-At: http://mailarchive.ietf.org/arch/msg/pce/m-2uFEXDefSRo3B3zD-dtBvcprI Subject: Re: [Pce] Adopting of draft-sivabalan-pce-segment-routing-03.txt as PCE WG Document X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Sep 2014 04:48:55 -0000 U3VwcG9ydC4NCg0KUmVnYXJkcyENCi1RaW4NCi0tLS0t08q8/tStvP4tLS0tLQ0Kt6K8/sjLOiBQ Y2UgW21haWx0bzpwY2UtYm91bmNlc0BpZXRmLm9yZ10gtPqx7SBKUCBWYXNzZXVyIChqdmFzc2V1 cikNCreiy83KsbzkOiAyMDE0xOo51MIxNMjVIDE4OjA2DQrK1bz+yMs6IHBjZUBpZXRmLm9yZw0K 1vfM4jogW1BjZV0gQWRvcHRpbmcgb2YgZHJhZnQtc2l2YWJhbGFuLXBjZS1zZWdtZW50LXJvdXRp bmctMDMudHh0IGFzIFBDRSBXRyBEb2N1bWVudA0KDQpEZWFyIFdHLA0KDQpXZSBoYWQgc2V2ZXJh bCBkaXNjdXNzaW9ucyBzaG93aW5nIGEgZ29vZCBjb25zZW5zdXMgYWRvcHRpbmcgZHJhZnQtc2l2 YWJhbGFuLXBjZS1zZWdtZW50LXJvdXRpbmctMDMudHh0IGFuZCB0aGlzIHdvcmsgaGFzIGNvbnNp ZGVyYWJseSBwcm9ncmVzc2VkIGluIG90aGVyIFdHLg0KDQpBcmUgeW91IGluIGZhdm9yIG9mIGFk b3B0aW5nIGRyYWZ0LXNpdmFiYWxhbi1wY2Utc2VnbWVudC1yb3V0aW5nLTAzLnR4dCBhcyBhIFBD RSBXRyBkb2N1bWVudCA/DQoNClRoYW5rcy4NCg0KSlAgYW5kIEp1bGllbi4NCg0KDQoNCg== From nobody Mon Sep 15 00:02:06 2014 Return-Path: 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 D30001A06C0 for ; Mon, 15 Sep 2014 00:02:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.601 X-Spam-Level: X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 WPR2th52Zzrq for ; Mon, 15 Sep 2014 00:02:02 -0700 (PDT) Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 59C881A06BC for ; Mon, 15 Sep 2014 00:02:02 -0700 (PDT) X-AuditID: c1b4fb3a-f79da6d0000008c7-6f-54168ee8a4d4 Received: from ESESSHC011.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id 6F.FF.02247.8EE86145; Mon, 15 Sep 2014 09:02:00 +0200 (CEST) Received: from ESESSMB301.ericsson.se ([169.254.1.77]) by ESESSHC011.ericsson.se ([153.88.183.51]) with mapi id 14.03.0174.001; Mon, 15 Sep 2014 09:01:59 +0200 From: Daniele Ceccarelli To: "JP Vasseur (jvasseur)" , "pce@ietf.org" Thread-Topic: Adopting of draft-sivabalan-pce-segment-routing-03.txt as PCE WG Document Thread-Index: AQHP0AOM1KLRLywSpUW4vDYHaosXcpwBxcBg Date: Mon, 15 Sep 2014 07:02:00 +0000 Message-ID: <4A1562797D64E44993C5CBF38CF1BE4812760BDC@ESESSMB301.ericsson.se> References: In-Reply-To: Accept-Language: it-IT, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [153.88.183.16] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrALMWRmVeSWpSXmKPExsUyM+Jvje6LPrEQg7Yl8hYztrxltmi6f4Pd gcljyu+NrB5LlvxkCmCK4rJJSc3JLEst0rdL4Mpo2HCSvWAia8Xma0+YGxgns3QxcnJICJhI TH2xiR3CFpO4cG89WxcjF4eQwFFGiR2HlkI5ixklHm+fxtjFyMHBJmAl8eSQD4gpIhAo0fg8 AaRXWCBC4uz9KWwgtohApMSH9btYIGwjiRtb94HFWQRUJY6f/A1m8wr4Spw+u48JxBYSsJHY enc2mM0pYCvx5/EDMJtRQFZiwu5FjCA2s4C4xK0n85kg7hSQWLLnPDOELSrx8vE/VghbUWLn 2XZmiHodiQW7P7FB2NoSyxa+ZobYKyhxcuYTlgmMorOQjJ2FpGUWkpZZSFoWMLKsYhQtTi0u zk03MtJLLcpMLi7Oz9PLSy3ZxAiMkoNbflvtYDz43PEQowAHoxIPb8Jd4RAh1sSy4srcQ4zS HCxK4rwLz80LFhJITyxJzU5NLUgtii8qzUktPsTIxMEp1cCos/x4pSGv5rR/R42cdu//ei68 973XmdJjWYxZNwNeLhYXye7+vMLsxdtsE4GHS9YFGP/Z1HbH4nuz7Xar9T8Z/t1cvOrjtE4D kbXmTxZp/jtTZ8a+SGjagpaZptWRO+7lBtZam1xolI2V6/asbn38qr3wy/5m+xOGSm5KF5dM MM79da5wJY+sEktxRqKhFnNRcSIA90u+NXMCAAA= Archived-At: http://mailarchive.ietf.org/arch/msg/pce/0JLWxQNg8-LrkOyAdXrP4ZrN3nk Subject: Re: [Pce] Adopting of draft-sivabalan-pce-segment-routing-03.txt as PCE WG Document X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Sep 2014 07:02:04 -0000 Yes, support BR Daniele > -----Original Message----- > From: Pce [mailto:pce-bounces@ietf.org] On Behalf Of JP Vasseur (jvasseur= ) > Sent: domenica 14 settembre 2014 12:06 > To: pce@ietf.org > Subject: [Pce] Adopting of draft-sivabalan-pce-segment-routing-03.txt as > PCE WG Document >=20 > Dear WG, >=20 > We had several discussions showing a good consensus adopting draft- > sivabalan-pce-segment-routing-03.txt and this work has considerably > progressed in other WG. >=20 > Are you in favor of adopting draft-sivabalan-pce-segment-routing-03.txt a= s a > PCE WG document ? >=20 > Thanks. >=20 > JP and Julien. >=20 >=20 From nobody Mon Sep 15 02:41:22 2014 Return-Path: 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 423E01A0712 for ; Mon, 15 Sep 2014 02:38:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.152 X-Spam-Level: X-Spam-Status: No, score=-2.152 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-1.652] 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 s_h9PzovjTF1 for ; Mon, 15 Sep 2014 02:38:50 -0700 (PDT) Received: from smtpjc.telefonica.com (smtpjc.telefonica.com [81.47.204.76]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4FE901A0724 for ; Mon, 15 Sep 2014 02:38:49 -0700 (PDT) Received: from smtpjc.telefonica.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 573EDE0192 for ; Mon, 15 Sep 2014 11:38:46 +0200 (CEST) Received: from ESTGVMSP101.EUROPE.telefonica.corp (unknown [10.92.4.9]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtpjc.telefonica.com (Postfix) with ESMTPS id 3E2C5E00E4 for ; Mon, 15 Sep 2014 11:38:46 +0200 (CEST) Received: from emea01-am1-obe.outbound.protection.outlook.com (10.92.5.139) by tls.telefonica.com (10.92.6.49) with Microsoft SMTP Server (TLS) id 14.3.195.1; Mon, 15 Sep 2014 11:38:45 +0200 Received: from DBXPR06MB365.eurprd06.prod.outlook.com (10.141.13.12) by DBXPR06MB366.eurprd06.prod.outlook.com (10.141.13.15) with Microsoft SMTP Server (TLS) id 15.0.1029.13; Mon, 15 Sep 2014 09:38:44 +0000 Received: from DBXPR06MB365.eurprd06.prod.outlook.com ([10.141.13.12]) by DBXPR06MB365.eurprd06.prod.outlook.com ([10.141.13.12]) with mapi id 15.00.1029.000; Mon, 15 Sep 2014 09:38:44 +0000 From: VICTOR LOPEZ ALVAREZ To: "pce@ietf.org" Thread-Topic: [Pce] Adopting of draft-sivabalan-pce-segment-routing-03.txt as PCE WG Document Thread-Index: AQHP0AOM1KLRLywSpUW4vDYHaosXcpwBxcBggABNZwA= Date: Mon, 15 Sep 2014 09:38:44 +0000 Message-ID: References: <4A1562797D64E44993C5CBF38CF1BE4812760BDC@ESESSMB301.ericsson.se> In-Reply-To: <4A1562797D64E44993C5CBF38CF1BE4812760BDC@ESESSMB301.ericsson.se> Accept-Language: es-ES, en-US Content-Language: es-ES X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.4.4.140807 x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [195.235.92.27] x-microsoft-antispam: BCL:0;PCL:0;RULEID:;UriScan:; x-forefront-prvs: 03355EE97E x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(41574002)(199003)(13464003)(189002)(51704005)(479174003)(4396001)(97736003)(95666004)(74502001)(2656002)(2501002)(31966008)(77982001)(74662001)(36756003)(90102001)(85852003)(105586002)(101416001)(83322001)(66066001)(46102001)(110136001)(92566001)(21056001)(85306004)(20776003)(107046002)(81342001)(15975445006)(76176999)(79102001)(19580405001)(99396002)(81542001)(54356999)(83072002)(87936001)(19580395003)(2351001)(80022001)(50986999)(86362001)(76482001)(106356001)(64706001)(107886001)(230783001)(106116001)(92726001); DIR:OUT; SFP:1102; SCL:1; SRVR:DBXPR06MB366; H:DBXPR06MB365.eurprd06.prod.outlook.com; FPR:; MLV:sfv; PTR:InfoNoRecords; A:1; MX:1; LANG:en; Content-Type: text/plain; charset="iso-8859-1" Content-ID: <4068FAC14F80F04D8B05C3FA3F311BDB@eurprd06.prod.outlook.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: telefonica.com X-TM-AS-MML: No Archived-At: http://mailarchive.ietf.org/arch/msg/pce/VTmbsmheWpHvqEC7zPtoJHp9gqM X-Mailman-Approved-At: Mon, 15 Sep 2014 02:41:19 -0700 Subject: Re: [Pce] Adopting of draft-sivabalan-pce-segment-routing-03.txt as PCE WG Document X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Sep 2014 09:38:53 -0000 Hi, Support as co-author. Thanks! Victor El 15/09/14 09:02, "Daniele Ceccarelli" escribi=F3: >Yes, support > >BR >Daniele > >> -----Original Message----- >> From: Pce [mailto:pce-bounces@ietf.org] On Behalf Of JP Vasseur >>(jvasseur) >> Sent: domenica 14 settembre 2014 12:06 >> To: pce@ietf.org >> Subject: [Pce] Adopting of draft-sivabalan-pce-segment-routing-03.txt as >> PCE WG Document >> >> Dear WG, >> >> We had several discussions showing a good consensus adopting draft- >> sivabalan-pce-segment-routing-03.txt and this work has considerably >> progressed in other WG. >> >> Are you in favor of adopting draft-sivabalan-pce-segment-routing-03.txt >>as a >> PCE WG document ? >> >> Thanks. >> >> JP and Julien. >> >> > >_______________________________________________ >Pce mailing list >Pce@ietf.org >https://www.ietf.org/mailman/listinfo/pce ________________________________ Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, pu= ede contener informaci=F3n privilegiada o confidencial y es para uso exclus= ivo de la persona o entidad de destino. Si no es usted. el destinatario ind= icado, queda notificado de que la lectura, utilizaci=F3n, divulgaci=F3n y/o= copia sin autorizaci=F3n puede estar prohibida en virtud de la legislaci= =F3n vigente. Si ha recibido este mensaje por error, le rogamos que nos lo = comunique inmediatamente por esta misma v=EDa y proceda a su destrucci=F3n. The information contained in this transmission is privileged and confidenti= al information intended only for the use of the individual or entity named = above. If the reader of this message is not the intended recipient, you are= hereby notified that any dissemination, distribution or copying of this co= mmunication is strictly prohibited. If you have received this transmission = in error, do not read it. Please immediately reply to the sender that you h= ave received this communication in error and then delete it. Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat=E1rio= , pode conter informa=E7=E3o privilegiada ou confidencial e =E9 para uso ex= clusivo da pessoa ou entidade de destino. Se n=E3o =E9 vossa senhoria o des= tinat=E1rio indicado, fica notificado de que a leitura, utiliza=E7=E3o, div= ulga=E7=E3o e/ou c=F3pia sem autoriza=E7=E3o pode estar proibida em virtude= da legisla=E7=E3o vigente. Se recebeu esta mensagem por erro, rogamos-lhe = que nos o comunique imediatamente por esta mesma via e proceda a sua destru= i=E7=E3o From nobody Mon Sep 15 02:51:06 2014 Return-Path: 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 4FD5E1A096C for ; Mon, 15 Sep 2014 02:51:05 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 n79fneXiXPSv for ; Mon, 15 Sep 2014 02:51:03 -0700 (PDT) Received: from relais-inet.francetelecom.com (relais-ias243.francetelecom.com [80.12.204.243]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2F3371A0936 for ; Mon, 15 Sep 2014 02:51:03 -0700 (PDT) Received: from omfeda07.si.francetelecom.fr (unknown [xx.xx.xx.200]) by omfeda12.si.francetelecom.fr (ESMTP service) with ESMTP id 009933B408B for ; Mon, 15 Sep 2014 11:51:01 +0200 (CEST) Received: from Exchangemail-eme2.itn.ftgroup (unknown [10.114.31.30]) by omfeda07.si.francetelecom.fr (ESMTP service) with ESMTP id CF106158052 for ; Mon, 15 Sep 2014 11:51:00 +0200 (CEST) Received: from OPEXCLILM34.corporate.adroot.infra.ftgroup ([169.254.4.215]) by OPEXCLILH02.corporate.adroot.infra.ftgroup ([10.114.31.30]) with mapi id 14.03.0195.001; Mon, 15 Sep 2014 11:51:01 +0200 From: To: "pce@ietf.org" Thread-Topic: [Pce] Adopting of draft-sivabalan-pce-segment-routing-03.txt as PCE WG Document Thread-Index: AQHP0AOMYz9GhUp9SjGGKUznZ45kE5wBxcBggABNZwD//+HlQA== Date: Mon, 15 Sep 2014 09:51:00 +0000 Message-ID: <7958_1410774660_5416B684_7958_1375_1_9E32478DFA9976438E7A22F69B08FF920A4D7B@OPEXCLILM34.corporate.adroot.infra.ftgroup> References: <4A1562797D64E44993C5CBF38CF1BE4812760BDC@ESESSMB301.ericsson.se> In-Reply-To: Accept-Language: fr-FR, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.168.234.1] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-PMX-Version: 6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2014.9.12.190919 Archived-At: http://mailarchive.ietf.org/arch/msg/pce/x4vz6L6BGNnG2sGvbY6IPWjQfPQ Subject: Re: [Pce] Adopting of draft-sivabalan-pce-segment-routing-03.txt as PCE WG Document X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Sep 2014 09:51:05 -0000 Support -----Original Message----- From: Pce [mailto:pce-bounces@ietf.org] On Behalf Of VICTOR LOPEZ ALVAREZ Sent: Monday, September 15, 2014 11:39 To: pce@ietf.org Subject: Re: [Pce] Adopting of draft-sivabalan-pce-segment-routing-03.txt a= s PCE WG Document Hi, Support as co-author. Thanks! Victor El 15/09/14 09:02, "Daniele Ceccarelli" escribi=F3: >Yes, support > >BR >Daniele > >> -----Original Message----- >> From: Pce [mailto:pce-bounces@ietf.org] On Behalf Of JP Vasseur >>(jvasseur) >> Sent: domenica 14 settembre 2014 12:06 >> To: pce@ietf.org >> Subject: [Pce] Adopting of draft-sivabalan-pce-segment-routing-03.txt=20 >>as PCE WG Document >> >> Dear WG, >> >> We had several discussions showing a good consensus adopting draft-=20 >> sivabalan-pce-segment-routing-03.txt and this work has considerably=20 >> progressed in other WG. >> >> Are you in favor of adopting=20 >>draft-sivabalan-pce-segment-routing-03.txt >>as a >> PCE WG document ? >> >> Thanks. >> >> JP and Julien. >> >> > >_______________________________________________ >Pce mailing list >Pce@ietf.org >https://www.ietf.org/mailman/listinfo/pce ________________________________ Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, pu= ede contener informaci=F3n privilegiada o confidencial y es para uso exclus= ivo de la persona o entidad de destino. Si no es usted. el destinatario ind= icado, queda notificado de que la lectura, utilizaci=F3n, divulgaci=F3n y/o= copia sin autorizaci=F3n puede estar prohibida en virtud de la legislaci= =F3n vigente. Si ha recibido este mensaje por error, le rogamos que nos lo = comunique inmediatamente por esta misma v=EDa y proceda a su destrucci=F3n. The information contained in this transmission is privileged and confidenti= al information intended only for the use of the individual or entity named = above. If the reader of this message is not the intended recipient, you are= hereby notified that any dissemination, distribution or copying of this co= mmunication is strictly prohibited. If you have received this transmission = in error, do not read it. Please immediately reply to the sender that you h= ave received this communication in error and then delete it. Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat=E1rio= , pode conter informa=E7=E3o privilegiada ou confidencial e =E9 para uso ex= clusivo da pessoa ou entidade de destino. Se n=E3o =E9 vossa senhoria o des= tinat=E1rio indicado, fica notificado de que a leitura, utiliza=E7=E3o, div= ulga=E7=E3o e/ou c=F3pia sem autoriza=E7=E3o pode estar proibida em virtude= da legisla=E7=E3o vigente. Se recebeu esta mensagem por erro, rogamos-lhe = que nos o comunique imediatamente por esta mesma via e proceda a sua destru= i=E7=E3o _______________________________________________ Pce mailing list Pce@ietf.org https://www.ietf.org/mailman/listinfo/pce ___________________________________________________________________________= ______________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confiden= tielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu= ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el= ectroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou = falsifie. Merci. This message and its attachments may contain confidential or privileged inf= ormation that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and dele= te this message and its attachments. As emails may be altered, Orange is not liable for messages that have been = modified, changed or falsified. Thank you. From nobody Mon Sep 15 03:39:10 2014 Return-Path: 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 EAD5C1A02CF for ; Mon, 15 Sep 2014 03:39:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.853 X-Spam-Level: X-Spam-Status: No, score=-5.853 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-1.652, 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 2MjWYWur0pIH for ; Mon, 15 Sep 2014 03:39:07 -0700 (PDT) Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C5D781A0700 for ; Mon, 15 Sep 2014 03:39:06 -0700 (PDT) Received: from 172.18.7.190 (EHLO lhreml401-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BJK74334; Mon, 15 Sep 2014 10:39:05 +0000 (GMT) Received: from SZXEML458-HUB.china.huawei.com (10.82.67.201) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 15 Sep 2014 11:39:04 +0100 Received: from szxeml556-mbs.china.huawei.com ([169.254.4.112]) by SZXEML458-HUB.china.huawei.com ([10.82.67.201]) with mapi id 14.03.0158.001; Mon, 15 Sep 2014 18:38:58 +0800 From: Dhruv Dhody To: "pce@ietf.org" Thread-Topic: [Pce] Survey on IRO Thread-Index: AQHPl6CzsYzM1lOzzEafMe8FKRuZD5wCch2Q Date: Mon, 15 Sep 2014 10:38:58 +0000 Message-ID: <23CE718903A838468A8B325B80962F9B865F23BC@szxeml556-mbs.china.huawei.com> Accept-Language: en-GB, zh-CN, en-US Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: x-originating-ip: [10.18.146.248] Content-Type: multipart/mixed; boundary="_003_23CE718903A838468A8B325B80962F9B865F23BCszxeml556mbschi_" MIME-Version: 1.0 X-CFilter-Loop: Reflected Archived-At: http://mailarchive.ietf.org/arch/msg/pce/vIeNdaDu9ujfmQJbQT-Gpu9eo3M Cc: "pce-chairs@tools.ietf.org" Subject: [Pce] FW: Survey on IRO X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Sep 2014 10:39:09 -0000 --_003_23CE718903A838468A8B325B80962F9B865F23BCszxeml556mbschi_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi All,=20 After discussion with the chairs, we would like to close this survey on Fri= day the 19th September.=20 For those of you who are yet to send the survey, please do that as soon as = possible directly to chairs.=20 For those who have submitted already, thanks a lot :) Dhruv > -----Original Message----- > From: Pce [mailto:pce-bounces@ietf.org] On Behalf Of Julien Meuric > Sent: 04 July 2014 23:57 > To: pce@ietf.org > Subject: [Pce] Survey on IRO >=20 > Hi PCE WG. >=20 > To address the issues associated with > draft-ietf-pce-pcep-domain-sequence and "Include Route Object" in PCEP, D= hruv > has proposed to start a small survey. If implementers agree that we need = to > clarify this, they would be much welcome to answer the attached questions= . >=20 > Dhruv will process the results, but to improve confidentiality, answers m= ay > be sent privately to the chairs. >=20 > Thanks, >=20 > JP & Julien, on behalf of Dhruv --_003_23CE718903A838468A8B325B80962F9B865F23BCszxeml556mbschi_ Content-Type: text/plain; name="IRO_Survey_Text.txt" Content-Description: IRO_Survey_Text.txt Content-Disposition: attachment; filename="IRO_Survey_Text.txt"; size=2091; creation-date="Fri, 04 Jul 2014 15:57:47 GMT"; modification-date="Fri, 04 Jul 2014 15:57:47 GMT" Content-ID: Content-Transfer-Encoding: base64 RHVyaW5nIGRpc2N1c3Npb24gb2YgZHJhZnQtaWV0Zi1wY2UtcGNlcC1kb21haW4tc2VxdWVuY2Ut MDQsIGl0IGhhcyBiZWVuDQpub3RlZCB0aGF0IFJGQzU0NDAgZG9lcyBub3QgZGVmaW5lIHdoZXRo ZXIgdGhlIHN1Yi1vYmplY3RzIGluIHRoZSBJUk8gDQphcmUgb3JkZXJlZCBvciB1bm9yZGVyZWQu DQoNCldlIHdvdWxkIGxpa2UgdG8gZG8gYW4gaW5mb3JtYWwgYW5kICpjb25maWRlbnRpYWwqIHN1 cnZleSBvZiBjdXJyZW50DQppbXBsZW1lbnRhdGlvbnMsIHRvIGhlbHAgY2xhcmlmeSB0aGlzIHNp dHVhdGlvbi4NCg0KMS4gSVJPIEVuY29kaW5nDQoNCiAgIGEuIERvZXMgeW91ciBpbXBsZW1lbnRh dGlvbiBjb25zdHJ1Y3QgSVJPPw0KDQogICBiLiBJZiB5b3VyIGFuc3dlciB0byBwYXJ0IChhKSBp cyBZZXMsIGRvZXMgeW91ciBpbXBsZW1lbnRhdGlvbg0KICAgICAgY29uc3RydWN0IHRoZSBJUk8g YXMgYW4gb3JkZXJlZCBsaXN0IGFsd2F5cywgc29tZXRpbWVzIG9yIG5ldmVyPw0KDQogICBjLiBJ ZiB5b3VyIGFuc3dlciB0byBwYXJ0IChiKSBpcyBTb21ldGltZXMsIHdoYXQgY3JpdGVyaWEgZG8g eW91IHVzZQ0KICAgICAgdG8gZGVjaWRlIGlmIHRoZSBJUk8gaXMgYW4gb3JkZXJlZCBvciB1bm9y ZGVyZWQgbGlzdD8NCg0KICAgZC4gSWYgeW91ciBhbnN3ZXIgdG8gcGFydCAoYikgaXMgQWx3YXlz IG9yIFNvbWV0aW1lcywgZG9lcyB5b3VyDQogICAgICBpbXBsZW1lbnRhdGlvbiBjb25zdHJ1Y3Qg dGhlIElSTyBhcyBhIHNlcXVlbmNlIG9mIHN0cmljdCBob3BzDQogICAgICBvciBhcyBhIHNlcXVl bmNlIG9mIGxvb3NlIGhvcHM/DQoNCjIuIElSTyBEZWNvZGluZw0KDQogICBhLiBEb2VzIHlvdXIg aW1wbGVtZW50YXRpb24gZGVjb2RlIElSTz8NCg0KICAgYi4gSWYgeW91ciBhbnN3ZXIgdG8gcGFy dCAoYSkgaXMgWWVzLCBkb2VzIHlvdXIgaW1wbGVtZW50YXRpb24NCiAgICAgIGludGVycHJldCB0 aGUgZGVjb2RlZCBJUk8gYXMgYW4gb3JkZXJlZCBsaXN0IGFsd2F5cywgc29tZXRpbWVzDQogICAg ICBvciBuZXZlcj8NCg0KICAgYy4gSWYgeW91ciBhbnN3ZXIgdG8gcGFydCAoYikgaXMgU29tZXRp bWVzLCB3aGF0IGNyaXRlcmlhIGRvIHlvdSB1c2UNCiAgICAgIHRvIGRlY2lkZSBpZiB0aGUgSVJP IGlzIGFuIG9yZGVyZWQgb3IgdW5vcmRlcmVkIGxpc3Q/DQoNCiAgIGQuIElmIHlvdXIgYW5zd2Vy IHRvIHBhcnQgKGIpIGlzIEFsd2F5cyBvciBTb21ldGltZXMsIGRvZXMgeW91cg0KICAgICAgaW1w bGVtZW50YXRpb24gaW50ZXJwcmV0IHRoZSBJUk8gYXMgYSBzZXF1ZW5jZSBvZiBzdHJpY3QgaG9w cw0KICAgICAgb3IgYXMgYSBzZXF1ZW5jZSBvZiBsb29zZSBob3BzPw0KDQozLiBJbXBhY3QNCg0K ICAgYS4gV2lsbCB0aGVyZSBiZSBhbiBpbXBhY3QgdG8geW91ciBpbXBsZW1lbnRhdGlvbiBpZiBS RkM1NDQwIGlzDQogICAgICB1cGRhdGVkIHRvIHN0YXRlIHRoYXQgdGhlIElSTyBpcyBhbiBvcmRl cmVkIGxpc3Q/DQoNCiAgIGIuIFdpbGwgdGhlcmUgYmUgYW4gaW1wYWN0IHRvIHlvdXIgaW1wbGVt ZW50YXRpb24gaWYgUkZDIDU0NDAgaXMNCiAgICAgIHVwZGF0ZWQgdG8gc3RhdGUgdGhhdCB0aGUg SVJPIGlzIGFuIHVub3JkZXJlZCBsaXN0Pw0KDQogICBjLiBJZiBSRkMgNTQ0MCBpcyB1cGRhdGVk IHRvIHN0YXRlIHRoYXQgdGhlIElSTyBpcyBhbiBvcmRlcmVkIGxpc3QsDQogICAgICB3aWxsIHRo ZXJlIGJlIGFuIGltcGFjdCB0byB5b3VyIGltcGxlbWVudGF0aW9uIGlmIFJGQyA1NDQwIGlzIGFs c28NCiAgICAgIHVwZGF0ZWQgdG8gYWxsb3cgSVJPIHN1Yi1vYmplY3RzIHRvIHVzZSB0aGUgbG9v c2UgYml0IChMLWJpdCk/DQoNCjQuIFJlc3BvbmRlbnRzDQoNCiAgIGEuIEFyZSB5b3UgYSBWZW5k b3IvUmVzZWFyY2ggTGFiL1NvZnR3YXJlIEhvdXNlL090aGVyIChwbGVhc2UNCiAgICAgIHNwZWNp ZnkpPyANCiAgICAgIA0KICAgYi4gSWYgeW91ciBhbnN3ZXIgdG8gcGFydCAoYSkgaXMgVmVuZG9y LCBpcyB0aGUgaW1wbGVtZW50YXRpb24gZm9yIGENCiAgICAgIHNoaXBwaW5nIHByb2R1Y3QsIHBy b2R1Y3QgdW5kZXIgZGV2ZWxvcG1lbnQgb3IgYSBwcm90b3R5cGU/ --_003_23CE718903A838468A8B325B80962F9B865F23BCszxeml556mbschi_ Content-Type: text/plain; name="ATT00001.txt" Content-Description: ATT00001.txt Content-Disposition: attachment; filename="ATT00001.txt"; size=124; creation-date="Fri, 04 Jul 2014 15:57:47 GMT"; modification-date="Fri, 04 Jul 2014 15:57:47 GMT" Content-ID: <582CD7C241D6E0449244DD8F38DC09ED@huawei.com> Content-Transfer-Encoding: base64 X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NClBjZSBtYWls aW5nIGxpc3QNClBjZUBpZXRmLm9yZw0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0 aW5mby9wY2UNCg== --_003_23CE718903A838468A8B325B80962F9B865F23BCszxeml556mbschi_-- From nobody Mon Sep 15 06:56:06 2014 Return-Path: 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 06F1C1A035C for ; Mon, 15 Sep 2014 06:56:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -16.153 X-Spam-Level: X-Spam-Status: No, score=-16.153 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.652, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 ZKQ6vWXfPQmQ for ; Mon, 15 Sep 2014 06:56:03 -0700 (PDT) Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5B22C1A0357 for ; Mon, 15 Sep 2014 06:56:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=423; q=dns/txt; s=iport; t=1410789360; x=1411998960; h=from:to:subject:date:message-id:in-reply-to:content-id: content-transfer-encoding:mime-version; bh=QGOPtQTv2SX3V4ia+8DwOow4qcah//QuxMOiHExL8Rw=; b=R0AZ/+ESoCzfLW1V/INu+rsVqj8swJvmyMqXN0TpIKFIzBDsE18xYks+ X1rPHcfPmLnzTppnv2js5qXezlhuqGX4yGsl1h1Wedh/ARUpB3SU+fU6g uQBX89wq4TTnD1ATwRfNNmId5otFAPobJLknx6ky0aP6gsoTlKmj0H0iu g=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AnAVAILvFlStJA2M/2dsb2JhbABggw2BKgSNSMRtAYESFniEBAIEOlEBCDZCJQIEARKIPrpWARePVIRLAQSPN4IWizuVP4IbgUNsgUiBAgEBAQ X-IronPort-AV: E=Sophos;i="5.04,528,1406592000"; d="scan'208";a="77984635" Received: from alln-core-7.cisco.com ([173.36.13.140]) by alln-iport-1.cisco.com with ESMTP; 15 Sep 2014 13:55:59 +0000 Received: from xhc-rcd-x11.cisco.com (xhc-rcd-x11.cisco.com [173.37.183.85]) by alln-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id s8FDtxIU012708 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for ; Mon, 15 Sep 2014 13:55:59 GMT Received: from xmb-aln-x07.cisco.com ([169.254.2.136]) by xhc-rcd-x11.cisco.com ([173.37.183.85]) with mapi id 14.03.0195.001; Mon, 15 Sep 2014 08:55:59 -0500 From: "Rakesh Gandhi (rgandhi)" To: "JP Vasseur (jvasseur)" , "pce@ietf.org" Thread-Topic: [Pce] Adoption of draft-sivabalan-pce-lsp-setup-type-02.txt as a PCE WG Document Thread-Index: AQHP0AOKhQXX3FptfUeVYEz+5mQyKZwCSkcA Date: Mon, 15 Sep 2014 13:55:58 +0000 Message-ID: In-Reply-To: <70E9F53F-3A40-4CC6-924B-9BA229FD84AA@cisco.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.3.5.130515 x-originating-ip: [10.86.240.12] Content-Type: text/plain; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/pce/2lJGEOkkJtO_XZI_AfIJPwZv59c Subject: Re: [Pce] Adoption of draft-sivabalan-pce-lsp-setup-type-02.txt as a PCE WG Document X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Sep 2014 13:56:04 -0000 Support. Thanks, Rakesh On 2014-09-14 6:06 AM, "JP Vasseur (jvasseur)" wrote: >Dear WG, > >We had several discussions showing a good consensus adopting >draft-sivabalan-pce-lsp-setup-type-02.txt and this work >has considerably progressed in other WG. > >Are you in favor of adopting draft-sivabalan-pce-lsp-setup-type-02.txt as >a PCE WG document ? > >Thanks. > >JP and Julien. From nobody Mon Sep 15 06:56:07 2014 Return-Path: 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 794C81A0357 for ; Mon, 15 Sep 2014 06:56:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -16.153 X-Spam-Level: X-Spam-Status: No, score=-16.153 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.652, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 J3V6ZSVdrTIs for ; Mon, 15 Sep 2014 06:55:58 -0700 (PDT) Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 111261A034D for ; Mon, 15 Sep 2014 06:55:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=436; q=dns/txt; s=iport; t=1410789350; x=1411998950; h=from:to:subject:date:message-id:in-reply-to:content-id: content-transfer-encoding:mime-version; bh=lBQxzad49E6u7SuMxJpN5nJrUBijh4p3x4TCRn1o884=; b=PoPMqX5V4OCsxE8bPjlcMP0j1um1IjpAJCf6JNtVXXvI5p4dk9VXlxl+ meQkP+VtNBJ03fzNZdeKCKvUmoi4dkTXCJJXnZFrVdrURFEesBvFWY8vd Qteb+Lr8UlRnMppKw3lbj9Stah+XbXWH+NYs9DI7Ejw07u8h3Aq1TeCE4 I=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgwFAILvFlStJA2F/2dsb2JhbABggw2BKgTSNQGBEhZ4hAQCBDpRAQg2QiUCBAESiD66VgEXj1SESwEEjzeCFos7lT+CG4FDbIFIgQIBAQE X-IronPort-AV: E=Sophos;i="5.04,528,1406592000"; d="scan'208";a="78040120" Received: from alln-core-11.cisco.com ([173.36.13.133]) by alln-iport-3.cisco.com with ESMTP; 15 Sep 2014 13:55:50 +0000 Received: from xhc-aln-x08.cisco.com (xhc-aln-x08.cisco.com [173.36.12.82]) by alln-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id s8FDtnIr005757 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for ; Mon, 15 Sep 2014 13:55:49 GMT Received: from xmb-aln-x07.cisco.com ([169.254.2.136]) by xhc-aln-x08.cisco.com ([173.36.12.82]) with mapi id 14.03.0195.001; Mon, 15 Sep 2014 08:55:48 -0500 From: "Rakesh Gandhi (rgandhi)" To: "JP Vasseur (jvasseur)" , "pce@ietf.org" Thread-Topic: [Pce] Adopting of draft-sivabalan-pce-segment-routing-03.txt as PCE WG Document Thread-Index: AQHP0AOM1KLRLywSpUW4vDYHaosXcpwCSjqA Date: Mon, 15 Sep 2014 13:55:47 +0000 Message-ID: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.3.5.130515 x-originating-ip: [10.86.240.12] Content-Type: text/plain; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/pce/jLJrgIp9LqdZVfQyz37HghzvmoY Subject: Re: [Pce] Adopting of draft-sivabalan-pce-segment-routing-03.txt as PCE WG Document X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Sep 2014 13:56:04 -0000 Support. Thanks, Rakesh On 2014-09-14 6:06 AM, "JP Vasseur (jvasseur)" wrote: >Dear WG, > >We had several discussions showing a good consensus adopting >draft-sivabalan-pce-segment-routing-03.txt and this work >has considerably progressed in other WG. > >Are you in favor of adopting draft-sivabalan-pce-segment-routing-03.txt >as a PCE WG document ? > >Thanks. > >JP and Julien. > > > From nobody Mon Sep 15 07:24:27 2014 Return-Path: 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 CDF9F1A0339 for ; Mon, 15 Sep 2014 07:23:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.852 X-Spam-Level: X-Spam-Status: No, score=-0.852 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RP_MATCHES_RCVD=-1.652] 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 W-QeC3KIJKXg for ; Mon, 15 Sep 2014 07:23:16 -0700 (PDT) Received: from server.riw.us (server.riw.us [162.144.32.236]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A11951A0367 for ; Mon, 15 Sep 2014 07:23:15 -0700 (PDT) Received: from 108-78-210-25.lightspeed.chrlnc.sbcglobal.net ([108.78.210.25]:61142 helo=RussPC) by server.riw.us with esmtpsa (UNKNOWN:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.82) (envelope-from ) id 1XTXBP-0000Uk-CC for pce@ietf.org; Mon, 15 Sep 2014 14:23:11 +0000 From: "Russ White" To: Date: Mon, 15 Sep 2014 10:22:55 -0400 Message-ID: <013e01cfd0f0$8be9fd90$a3bdf8b0$@riw.us> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 15.0 Thread-Index: Ac/Q8ICcHC73aCtRRSehjfSBrpsTvA== Content-Language: en-us X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - server.riw.us X-AntiAbuse: Original Domain - ietf.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - riw.us X-Get-Message-Sender-Via: server.riw.us: authenticated_id: russw@riw.us X-Source: X-Source-Args: X-Source-Dir: Archived-At: http://mailarchive.ietf.org/arch/msg/pce/jFcLTiBWyd_2Ab9LKMfzIguiOAc X-Mailman-Approved-At: Mon, 15 Sep 2014 07:24:26 -0700 Subject: [Pce] draft-sivabalan-pce-segment-routing-03.txt X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Sep 2014 14:23:17 -0000 Y'all: Somehow lost the original message -- I would support draft-sivabalan-pce-segment-routing-03.txt as a WG doc. :-) Russ From nobody Mon Sep 15 08:10:56 2014 Return-Path: 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 71EC61A0370 for ; Mon, 15 Sep 2014 08:10:38 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 FQlRU7kmgGVZ for ; Mon, 15 Sep 2014 08:10:36 -0700 (PDT) Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1166A1A036E for ; Mon, 15 Sep 2014 08:10:36 -0700 (PDT) Received: from omfedm06.si.francetelecom.fr (unknown [xx.xx.xx.2]) by omfedm13.si.francetelecom.fr (ESMTP service) with ESMTP id 3F1CE3242A8; Mon, 15 Sep 2014 17:10:34 +0200 (CEST) Received: from Exchangemail-eme2.itn.ftgroup (unknown [10.114.31.16]) by omfedm06.si.francetelecom.fr (ESMTP service) with ESMTP id 2313B27C064; Mon, 15 Sep 2014 17:10:34 +0200 (CEST) Received: from OPEXCLILM34.corporate.adroot.infra.ftgroup ([169.254.4.159]) by OPEXCLILH05.corporate.adroot.infra.ftgroup ([10.114.31.16]) with mapi id 14.03.0195.001; Mon, 15 Sep 2014 17:10:33 +0200 From: To: "JP Vasseur (jvasseur)" , "pce@ietf.org" Thread-Topic: [Pce] Adoption of draft-sivabalan-pce-lsp-setup-type-02.txt as a PCE WG Document Thread-Index: AQHP0AOKNAHoeC/GTHmp5sftEmaGMJwCSkcAgAAEDXA= Date: Mon, 15 Sep 2014 15:10:33 +0000 Message-ID: <21820_1410793834_5417016A_21820_6219_1_9E32478DFA9976438E7A22F69B08FF920A4F35@OPEXCLILM34.corporate.adroot.infra.ftgroup> References: <70E9F53F-3A40-4CC6-924B-9BA229FD84AA@cisco.com> In-Reply-To: Accept-Language: fr-FR, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.168.234.3] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-PMX-Version: 6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2014.9.15.132720 Archived-At: http://mailarchive.ietf.org/arch/msg/pce/YF20IGAldyNVA12OT_17y01ANIc Subject: Re: [Pce] Adoption of draft-sivabalan-pce-lsp-setup-type-02.txt as a PCE WG Document X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Sep 2014 15:10:38 -0000 Support -----Original Message----- From: Pce [mailto:pce-bounces@ietf.org] On Behalf Of Rakesh Gandhi (rgandhi) Sent: Monday, September 15, 2014 15:56 To: JP Vasseur (jvasseur); pce@ietf.org Subject: Re: [Pce] Adoption of draft-sivabalan-pce-lsp-setup-type-02.txt as= a PCE WG Document Support. Thanks, Rakesh On 2014-09-14 6:06 AM, "JP Vasseur (jvasseur)" wrote: >Dear WG, > >We had several discussions showing a good consensus adopting=20 >draft-sivabalan-pce-lsp-setup-type-02.txt and this work has=20 >considerably progressed in other WG. > >Are you in favor of adopting draft-sivabalan-pce-lsp-setup-type-02.txt=20 >as a PCE WG document ? > >Thanks. > >JP and Julien. _______________________________________________ Pce mailing list Pce@ietf.org https://www.ietf.org/mailman/listinfo/pce ___________________________________________________________________________= ______________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confiden= tielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu= ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el= ectroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou = falsifie. Merci. This message and its attachments may contain confidential or privileged inf= ormation that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and dele= te this message and its attachments. As emails may be altered, Orange is not liable for messages that have been = modified, changed or falsified. Thank you. From nobody Mon Sep 15 09:24:04 2014 Return-Path: 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 EC71B1A6F20 for ; Mon, 15 Sep 2014 09:24:01 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.03 X-Spam-Level: X-Spam-Status: No, score=-3.03 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-1.652, 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 oYyVpFRBDQZK for ; Mon, 15 Sep 2014 09:23:57 -0700 (PDT) Received: from mail-oi0-x22c.google.com (mail-oi0-x22c.google.com [IPv6:2607:f8b0:4003:c06::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 317BA1A7D84 for ; Mon, 15 Sep 2014 09:01:56 -0700 (PDT) Received: by mail-oi0-f44.google.com with SMTP id x69so2696104oia.3 for ; Mon, 15 Sep 2014 09:01:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=wfMMvV8p0GU8+2ShivlMjYRt/Q4RUVsMsW/4scxuv90=; b=CM/drdsmYHzmQW/tNuf5pA1nbrY2LuUSbGjmFAt34gsfVr8gedZRv4Jpd79esqkj9w I+w15sVYEqrScrgwiErzmYvVK8TjR/OLFLQ+JXqxhG5E+zXeNQFFYUWVGmAxViPqalfK fdPaSmP9FLKDUHY9DXyq34NSAl34gskgC9Kxm/yuT5ok/lg7J3rHZsLMfm3sbhK29hRH iVkoZk9IPTTK6Iypyx4ggD2NgMiczqqfscqiJ1kyhRQK95pc8PpfjsoDjtfr7WSnlGBA KYvDFJoXCqwYKSTkEoHyAwsqYvNvFz+uAi0Fp8PqEXJ2h2P8gwl6PxZBMygogNFJSHnW iKhQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=wfMMvV8p0GU8+2ShivlMjYRt/Q4RUVsMsW/4scxuv90=; b=eF5WnSqpENKE8YhBrVlrhfN0wBRrx/OV/e/5U6vd5NxepJ4Av7tUgPD0o7u0NA03Bd Y1aX/sgkIjr2Vbc7YQNIVc/ZQCfkNUfwrY6FzWjybsoj5qi3Qxv0jgNX5FKXZxQDLKmT f0CcsFQufq9mtTG6buVksDusmL4Cvob1u2C1gAyYWOsC5RD7ZbU/5qfBhk4UFXKde6Kb ZbIPLVbObKFYM/dbOj31qp7mGCCAmdSmsDkHoonTXg2jerCYey9zDJiSo76L7La0v5bq tflStP/d4H03fiQhhM41gaMYC62XOUfnaoBDZoKPElvMvJAnQHWS00LV2DWTSozNWAWr pi2Q== X-Gm-Message-State: ALoCoQmgURn8g9Dsq85aaEW32Nbgerr8fHvhthVJ9fStESJlbicCK9I04xJP4LzXVoYmqD1QgmGy MIME-Version: 1.0 X-Received: by 10.182.142.40 with SMTP id rt8mr4025710obb.80.1410796915202; Mon, 15 Sep 2014 09:01:55 -0700 (PDT) Received: by 10.182.26.18 with HTTP; Mon, 15 Sep 2014 09:01:55 -0700 (PDT) In-Reply-To: <70E9F53F-3A40-4CC6-924B-9BA229FD84AA@cisco.com> References: <70E9F53F-3A40-4CC6-924B-9BA229FD84AA@cisco.com> Date: Mon, 15 Sep 2014 09:01:55 -0700 Message-ID: From: Ina Minei To: "JP Vasseur (jvasseur)" Content-Type: multipart/alternative; boundary=001a11c2de6efb304105031cc0b4 Archived-At: http://mailarchive.ietf.org/arch/msg/pce/d4PBdCPlIhtIDXP0AvbC4R2iaUI Cc: "pce@ietf.org" Subject: Re: [Pce] Adoption of draft-sivabalan-pce-lsp-setup-type-02.txt as a PCE WG Document X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Sep 2014 16:24:02 -0000 --001a11c2de6efb304105031cc0b4 Content-Type: text/plain; charset=UTF-8 support as co-author. On Sun, Sep 14, 2014 at 3:06 AM, JP Vasseur (jvasseur) wrote: > Dear WG, > > We had several discussions showing a good consensus adopting > draft-sivabalan-pce-lsp-setup-type-02.txt and this work > has considerably progressed in other WG. > > Are you in favor of adopting draft-sivabalan-pce-lsp-setup-type-02.txt as > a PCE WG document ? > > Thanks. > > JP and Julien. > > _______________________________________________ > Pce mailing list > Pce@ietf.org > https://www.ietf.org/mailman/listinfo/pce > > --001a11c2de6efb304105031cc0b4 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
support as co-author.

=
On Sun, Sep 14, 2014 at 3:06 AM, JP Vasseur (jva= sseur) <jvasseur@cisco.com> wrote:
Dear WG,

We had several discussions showing a good consensus adopting draft-sivabala= n-pce-lsp-setup-type-02.txt and this work
has considerably progressed in other WG.

Are you in favor of adopting draft-sivabalan-pce-lsp-setup-type-02.txt as a= PCE WG document ?

Thanks.

JP and Julien.

_______________________________________________
Pce mailing list
Pce@ietf.org
htt= ps://www.ietf.org/mailman/listinfo/pce


--001a11c2de6efb304105031cc0b4-- From nobody Mon Sep 15 09:26:37 2014 Return-Path: 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 2F3C71A8027 for ; Mon, 15 Sep 2014 09:26:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.03 X-Spam-Level: X-Spam-Status: No, score=-3.03 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-1.652, 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 iD6RWWDG-cAU for ; Mon, 15 Sep 2014 09:26:34 -0700 (PDT) Received: from mail-ob0-x231.google.com (mail-ob0-x231.google.com [IPv6:2607:f8b0:4003:c01::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7F6271A6FEB for ; Mon, 15 Sep 2014 09:03:17 -0700 (PDT) Received: by mail-ob0-f177.google.com with SMTP id wp4so2575241obc.22 for ; Mon, 15 Sep 2014 09:03:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=yf4tQ8/ZwVSQu7ycoh9W+Khx59Q2r/waNBxdkGG7mOM=; b=oUM2OktGOpCKw5uTsCyyyIuw4yBZtViCD20xz6OZ2h6A1VCLrj4fHz1a4uHcTuII5y jgxAdb/9ksAIyIphDlPVs47yLATb+4wZnE+CVy9f3LEFNeW+mBUtCsdiI7fNcWaUAgzH BFhDY9mwU2s8Kk7m0gi0lNBfcjFv4wr3r4eGrKGoZPcT0+qR7iA9U3RVj/6VYJk9VkbX Tc8B863GHF87mAXL47Rw8qSUihWkIiPLcR3ampy1oQHF/pFM8xxHndr4cwkGWk7fz78m XXOuzm2d2/n563gAukaPbn4qi9Hq+0CxIiM3oHap1SWKTXLLE2Su2CPwbds70Ud3Ga/a Jb4w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=yf4tQ8/ZwVSQu7ycoh9W+Khx59Q2r/waNBxdkGG7mOM=; b=GlxWUNeqm/UjeVS97ceMKqRSb0hh5GptaWtBPvZ6X4IMaxqonq5NGMlha41LSniroh mqhb6Jwq4Ur6+Nmh95lX92H1z6j4GRRCEl/A+/ZGWeT4avt29PgLRbYdorRBls0i9UvR hO4/9LusUWGjWH25jKame9mzGAfHdhQ2/MeexgYpu9c1Ga7PgT1tdfDAxhOUbxgnJHNW 5EZzemC3/RF5a6ixrrxrKcF2Dnl/M6wczxrRcZW2yGRhkdgulJqgIqW52AyPlfzpGiV/ ff5kp3yUDw8vrrOXROTfUeBOrUyFgjwKCX4aps5WFZo3D9gC3bKh9DHIl14FwuGDx484 ob1Q== X-Gm-Message-State: ALoCoQn5YEg6DKrF1z7OOncqBirlPQZmsEkIWJa1I8Ub5XO1fYJsuu50QPzu6BLaxprSCIqf4JuH MIME-Version: 1.0 X-Received: by 10.60.15.37 with SMTP id u5mr4913294oec.61.1410796994129; Mon, 15 Sep 2014 09:03:14 -0700 (PDT) Received: by 10.182.26.18 with HTTP; Mon, 15 Sep 2014 09:03:14 -0700 (PDT) In-Reply-To: References: Date: Mon, 15 Sep 2014 09:03:14 -0700 Message-ID: From: Ina Minei To: "JP Vasseur (jvasseur)" Content-Type: multipart/alternative; boundary=089e013cbd82af91bb05031cc526 Archived-At: http://mailarchive.ietf.org/arch/msg/pce/dIJZQ2m3WPXFl2PNXZYlOd9tYhs Cc: "pce@ietf.org" Subject: Re: [Pce] Adopting of draft-sivabalan-pce-segment-routing-03.txt as PCE WG Document X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Sep 2014 16:26:36 -0000 --089e013cbd82af91bb05031cc526 Content-Type: text/plain; charset=UTF-8 support On Sun, Sep 14, 2014 at 3:06 AM, JP Vasseur (jvasseur) wrote: > Dear WG, > > We had several discussions showing a good consensus adopting > draft-sivabalan-pce-segment-routing-03.txt and this work > has considerably progressed in other WG. > > Are you in favor of adopting draft-sivabalan-pce-segment-routing-03.txt as > a PCE WG document ? > > Thanks. > > JP and Julien. > > > > > _______________________________________________ > Pce mailing list > Pce@ietf.org > https://www.ietf.org/mailman/listinfo/pce > > --089e013cbd82af91bb05031cc526 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
support

On Sun, Sep 14, 2014 at 3:06 AM, JP Vasseur (jvasseur) <jvas= seur@cisco.com> wrote:
Dear= WG,

We had several discussions showing a good consensus adopting draft-sivabala= n-pce-segment-routing-03.txt and this work
has considerably progressed in other WG.

Are you in favor of adopting draft-sivabalan-pce-segment-routing-03.txt as = a PCE WG document ?

Thanks.

JP and Julien.




_______________________________________________
Pce mailing list
Pce@ietf.org
htt= ps://www.ietf.org/mailman/listinfo/pce


--089e013cbd82af91bb05031cc526-- From nobody Mon Sep 15 10:40:53 2014 Return-Path: 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 9D5A81A6FA8 for ; Mon, 15 Sep 2014 10:40:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -16.153 X-Spam-Level: X-Spam-Status: No, score=-16.153 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.652, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 p-a4BD07HArt for ; Mon, 15 Sep 2014 10:40:47 -0700 (PDT) Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AB9601ACD55 for ; Mon, 15 Sep 2014 09:53:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=433; q=dns/txt; s=iport; t=1410800003; x=1412009603; h=from:to:subject:date:message-id:content-id: content-transfer-encoding:mime-version; bh=LCnF/G/kbxgMAG1tvao1aNkeDo5NCiTJ34yHE1FScxg=; b=g/oUWUl9Wqnz4TR/I0zqOvVKAqYRIiUeuNm++pjVbgbpu4KQY0yjxdZe 2tDP45S5l4A6WYly4pOXpGcQ8TsaIur1cQ9mtZPwoopaXwyNymkYC+7NN e1RZfN525+M14ifvRSq4AbNnegcSuUA2t4+89vnAKWK+3tUc5FfzjKSnZ k=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgoFAAEZF1StJV2b/2dsb2JhbABggw2BKgTTTRZ4hAQCBDpRAQg2QicEARKIPrtDAReUHwWPN4IWizuVP4IbgUNsgUiBAgEBAQ X-IronPort-AV: E=Sophos;i="5.04,529,1406592000"; d="scan'208";a="355349630" Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-7.cisco.com with ESMTP; 15 Sep 2014 16:53:22 +0000 Received: from xhc-rcd-x01.cisco.com (xhc-rcd-x01.cisco.com [173.37.183.75]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s8FGrLTM006162 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for ; Mon, 15 Sep 2014 16:53:21 GMT Received: from xmb-aln-x08.cisco.com ([169.254.3.10]) by xhc-rcd-x01.cisco.com ([173.37.183.75]) with mapi id 14.03.0195.001; Mon, 15 Sep 2014 11:53:21 -0500 From: "Tarek Saad (tsaad)" To: "JP Vasseur (jvasseur)" , "pce@ietf.org" Thread-Topic: [Pce] Adopting of draft-sivabalan-pce-segment-routing-03.txt as PCE WG Document Thread-Index: AQHP0QWO1KLRLywSpUW4vDYHaosXcg== Date: Mon, 15 Sep 2014 16:53:21 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.4.4.140807 x-originating-ip: [161.44.213.10] Content-Type: text/plain; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/pce/fp9CSo9AY5C0R1Oms0rcgy7Qxe4 Subject: Re: [Pce] Adopting of draft-sivabalan-pce-segment-routing-03.txt as PCE WG Document X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Sep 2014 17:40:51 -0000 Support. Regards, Tarek On 2014-09-14, 6:06 AM, "JP Vasseur (jvasseur)" wrote: >Dear WG, > >We had several discussions showing a good consensus adopting >draft-sivabalan-pce-segment-routing-03.txt and this work >has considerably progressed in other WG. > >Are you in favor of adopting draft-sivabalan-pce-segment-routing-03.txt >as a PCE WG document ? > >Thanks. > >JP and Julien. > > > From nobody Mon Sep 15 11:17:50 2014 Return-Path: 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 864C81A8735 for ; Mon, 15 Sep 2014 11:17:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.266 X-Spam-Level: X-Spam-Status: No, score=-2.266 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_LOW=-0.7, 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 Suz1qfNYqRS6 for ; Mon, 15 Sep 2014 11:17:44 -0700 (PDT) Received: from mx0b-00103a01.pphosted.com (mx0b-00103a01.pphosted.com [67.231.152.227]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BD2F41ACE73 for ; Mon, 15 Sep 2014 10:32:09 -0700 (PDT) Received: from pps.filterd (m0002317.ppops.net [127.0.0.1]) by mx0b-00103a01.pphosted.com (8.14.5/8.14.5) with SMTP id s8FHU8e7005649; Mon, 15 Sep 2014 13:32:05 -0400 Received: from vawvcgsie2k1302.ciena.com (LIN1-118-36-36.ciena.com [63.118.36.36]) by mx0b-00103a01.pphosted.com with ESMTP id 1pe2ktrdbd-1 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Mon, 15 Sep 2014 13:32:05 -0400 Received: from ONWVEXCHHT04.ciena.com (10.128.6.44) by VAWVCGSIE2K1302.ciena.com (10.4.62.16) with Microsoft SMTP Server (TLS) id 15.0.847.32; Mon, 15 Sep 2014 13:32:05 -0400 Received: from ONWVEXCHMB04.ciena.com ([::1]) by ONWVEXCHHT04.ciena.com ([::1]) with mapi; Mon, 15 Sep 2014 13:32:03 -0400 From: "Shah, Himanshu" To: "JP Vasseur (jvasseur)" , "pce@ietf.org" Date: Mon, 15 Sep 2014 13:32:03 -0400 Thread-Topic: WG Last Call on draft-ietf-pce-stateful-pce-app-02 and draft-ietf-pce-stateful-pce-09 Thread-Index: AQHP0ARVQD5F3VY9REKwNcdOFPjV1JwCdc4A Message-ID: <40746B2300A8FC4AB04EE722A593182B79240A14@ONWVEXCHMB04.ciena.com> References: In-Reply-To: Accept-Language: en-US, en-CA Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, en-CA x-tm-as-product-ver: SMEX-10.0.0.1412-7.000.1014-20954.001 x-tm-as-result: No--48.419400-8.000000-31 x-tm-as-user-approved-sender: No x-tm-as-user-blocked-sender: No Content-Type: multipart/alternative; boundary="_000_40746B2300A8FC4AB04EE722A593182B79240A14ONWVEXCHMB04cie_" MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.12.52, 1.0.28, 0.0.0000 definitions=2014-09-15_04:2014-09-15,2014-09-15,1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1402240000 definitions=main-1409150148 Archived-At: http://mailarchive.ietf.org/arch/msg/pce/Lt5w-PnY1b7XETs89bQ5e-x9xS0 Subject: Re: [Pce] WG Last Call on draft-ietf-pce-stateful-pce-app-02 and draft-ietf-pce-stateful-pce-09 X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Sep 2014 18:17:46 -0000 --_000_40746B2300A8FC4AB04EE722A593182B79240A14ONWVEXCHMB04cie_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Support. /himanshu From: Pce [mailto:pce-bounces@ietf.org] On Behalf Of JP Vasseur (jvasseur) Sent: Sunday, September 14, 2014 6:12 AM To: pce@ietf.org Subject: [Pce] WG Last Call on draft-ietf-pce-stateful-pce-app-02 and draft= -ietf-pce-stateful-pce-09 Dear WG, Both draft-ietf-pce-stateful-pce-app-02 and draft-ietf-pce-stateful-pce-09 = are now stable ready for WG Last Call. This starts a 3-week WG Last call, which will end on Oct 6 at noon ET. Please send your comments on the mailing list. ps: this WG LC will be followed by another WG LC on draft-ietf-pce-stateful= -sync-optimizations-01 and draft-ietf-pce-pce-initiated-lsp-01. Thanks. JP and Julien. --_000_40746B2300A8FC4AB04EE722A593182B79240A14ONWVEXCHMB04cie_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Support.<= o:p>

/himanshu

 

<= div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0= in 0in'>

From: Pce [mailto:pce-bounces@ietf.org] On Be= half Of JP Vasseur (jvasseur)
Sent: Sunday, September 14, 201= 4 6:12 AM
To: pce@ietf.org
Subject: [Pce] WG Last Call = on draft-ietf-pce-stateful-pce-app-02 and draft-ietf-pce-stateful-pce-09

 

Dear WG,

&n= bsp;

Both draft-ietf-pce-stateful-= pce-app-02 and draft-ietf-pce-stateful-pce-09 are now stable ready for WG L= ast Call.

This starts a 3-wee= k WG Last call, which will end on Oct 6 at noon ET.

 

Please send your comments on the mailing list.

=

 

ps: this WG LC will be followed by another WG LC on draft-ietf-= pce-stateful-sync-optimizations-01

and draft-ietf-pce-pce-initiated-lsp-01.

 

 

Thanks.

 

JP and Julien.

= --_000_40746B2300A8FC4AB04EE722A593182B79240A14ONWVEXCHMB04cie_-- From nobody Mon Sep 15 12:15:58 2014 Return-Path: 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 4D4351A03D8 for ; Mon, 15 Sep 2014 12:15:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.601 X-Spam-Level: X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 Z7_n41p21k4F for ; Mon, 15 Sep 2014 12:15:56 -0700 (PDT) Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9F0551A6F39 for ; Mon, 15 Sep 2014 12:09:44 -0700 (PDT) X-AuditID: c618062d-f79206d0000014d2-11-5416e3aeb2be Received: from EUSAAHC005.ericsson.se (Unknown_Domain [147.117.188.87]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id 76.5B.05330.EA3E6145; Mon, 15 Sep 2014 15:03:43 +0200 (CEST) Received: from EUSAAMB109.ericsson.se ([147.117.188.126]) by EUSAAHC005.ericsson.se ([147.117.188.87]) with mapi id 14.03.0174.001; Mon, 15 Sep 2014 15:09:35 -0400 From: Jeff Tantsura To: "JP Vasseur (jvasseur)" , "pce@ietf.org" Thread-Topic: [Pce] Adoption of draft-sivabalan-pce-lsp-setup-type-02.txt as a PCE WG Document Thread-Index: AQHP0AOKhQXX3FptfUeVYEz+5mQyKZwCSkcAgAAUwAA= Date: Mon, 15 Sep 2014 19:09:34 +0000 Message-ID: References: <70E9F53F-3A40-4CC6-924B-9BA229FD84AA@cisco.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.4.3.140616 x-originating-ip: [147.117.188.11] Content-Type: text/plain; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrKLMWRmVeSWpSXmKPExsUyuXRPuO76x2IhBn8PcVvM2PKW2aLp/g12 ByaPKb83snosWfKTKYApissmJTUnsyy1SN8ugSvjy677bAWPmSvmdsk1ME5i7mLk5JAQMJFY P2U2G4QtJnHh3nogm4tDSOAoo8SnR7vZIZzljBL/D3aDdbAJGEj8/3acpYuRg0NEIFCi8XkC SFhYIF7iWOMmsEEiAgkSe1+eZYWwrSRurDgNFmcRUJVYd3AfmM0rYC5xvGsGI4gtJJAo8eLK IrDxnAL6EqenzACzGYEO+n5qDROIzSwgLnHryXwmiEMFJJbsOQ/1gKjEy8f/wHaJCuhJfJpy DqpGSeLj7/nsEL06Egt2f2IDOZlZwFriy4loiLC2xLKFr5khzhGUODnzCcsERvFZSLbNQtI9 C6F7FpLuWUi6FzCyrmLkKC1OLctNNzLYxAiMp2MSbLo7GPe8tDzEKMDBqMTDq+AhFiLEmlhW XJl7iFGag0VJnHdW7bxgIYH0xJLU7NTUgtSi+KLSnNTiQ4xMHJxSDYw8sw29LyUJHfvTWp79 aEtp1GKRsxFc8qvcN+tvv2j6y4ctVVd2f7rhLv9F+pPstXYvm+WSedgouMWn69jC59xne+3T ReStCoKYQ8PU61LZOQLYA5qu+1Vs9tFoqg4RjHb82ezJ/G/Z5tyWtvkrl+1ZGHtPSSGj6v3G +utuCxa8DlP9fDXvhRJLcUaioRZzUXEiALKQ5PSIAgAA Archived-At: http://mailarchive.ietf.org/arch/msg/pce/psKnzeHNblhQNtt3W2NNU7VbCRA Subject: Re: [Pce] Adoption of draft-sivabalan-pce-lsp-setup-type-02.txt as a PCE WG Document X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Sep 2014 19:15:57 -0000 Yes/support Cheers, Jeff >> >>We had several discussions showing a good consensus adopting >>draft-sivabalan-pce-lsp-setup-type-02.txt and this work >>has considerably progressed in other WG. >> >>Are you in favor of adopting draft-sivabalan-pce-lsp-setup-type-02.txt as >>a PCE WG document ? >> >>Thanks. >> >>JP and Julien. > >_______________________________________________ >Pce mailing list >Pce@ietf.org >https://www.ietf.org/mailman/listinfo/pce From nobody Mon Sep 15 12:54:48 2014 Return-Path: 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 65E511A6FCE for ; Mon, 15 Sep 2014 12:54:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -16.153 X-Spam-Level: X-Spam-Status: No, score=-16.153 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.652, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 hY3idF6-ZbFr for ; Mon, 15 Sep 2014 12:54:42 -0700 (PDT) Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 52FC31A6FBF for ; Mon, 15 Sep 2014 12:54:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1048; q=dns/txt; s=iport; t=1410810878; x=1412020478; h=from:to:cc:subject:date:message-id: content-transfer-encoding:mime-version; bh=K5TzrRFexUJH65lVwPW6jm5RDwNO+31D76RXMYrpGuk=; b=Gd6OXIxdG3TqTjFw2eM2iwqthxx+Ujlrfy94XINaXfIzAxagBhhhxqcF JHCUPQjPYjl5CQr53mvnQTzMdZeFGkRg+UYf4AYYF/H7xD5aYfGwMscT4 DNMM9OWtl5C0RBWvn0QR7RMtz76LDp99TvQKYpk0TT+FTKm8bxqHGHwuU 0=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ag0FACxDF1StJV2b/2dsb2JhbABggw2BKgTSPQGBGhZ4hAMBAQEEOj8SAQgRAwECCxRCHQkBBA4FCIg2u04BF48cMQ2DKIEdBY83ghageoNebIFIgQIBAQE X-IronPort-AV: E=Sophos;i="5.04,530,1406592000"; d="scan'208";a="78151744" Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by alln-iport-6.cisco.com with ESMTP; 15 Sep 2014 19:54:37 +0000 Received: from xhc-aln-x10.cisco.com (xhc-aln-x10.cisco.com [173.36.12.84]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s8FJsbja002440 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 15 Sep 2014 19:54:37 GMT Received: from xmb-rcd-x13.cisco.com ([169.254.3.249]) by xhc-aln-x10.cisco.com ([173.36.12.84]) with mapi id 14.03.0195.001; Mon, 15 Sep 2014 14:54:37 -0500 From: "Siva Sivabalan (msiva)" To: "pce@ietf.org" Thread-Topic: [Pce] Adoption of draft-sivabalan-pce-lsp-setup-type-02.txt Thread-Index: Ac/RHt25EIvY/htgRli7kSfgAWs7/Q== Date: Mon, 15 Sep 2014 19:54:36 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [161.44.212.199] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/pce/-a-Do1AGV8I4cnnuDlJTntcFgTo Subject: Re: [Pce] Adoption of draft-sivabalan-pce-lsp-setup-type-02.txt X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Sep 2014 19:54:46 -0000 Support as a co-author. Thanks, Siva =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Date: Sun, 14 Sep 2014 10:06:24 +0000 From: "JP Vasseur (jvasseur)" To: "pce@ietf.org" Subject: [Pce] Adoption of draft-sivabalan-pce-lsp-setup-type-02.txt as a PCE WG Document Message-ID: <70E9F53F-3A40-4CC6-924B-9BA229FD84AA@cisco.com> Content-Type: text/plain; charset=3D"us-ascii" Dear WG, We had several discussions showing a good consensus adopting draft-sivabala= n-pce-lsp-setup-type-02.txt and this work has considerably progressed in ot= her WG. Are you in favor of adopting draft-sivabalan-pce-lsp-setup-type-02.txt as a= PCE WG document ? Thanks. JP and Julien. From nobody Mon Sep 15 12:57:09 2014 Return-Path: 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 3A1AD1A6FD3 for ; Mon, 15 Sep 2014 12:57:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -16.153 X-Spam-Level: X-Spam-Status: No, score=-16.153 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.652, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 QFoHe4komitG for ; Mon, 15 Sep 2014 12:57:06 -0700 (PDT) Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 191D81A6FF8 for ; Mon, 15 Sep 2014 12:56:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1054; q=dns/txt; s=iport; t=1410811012; x=1412020612; h=from:to:cc:subject:date:message-id: content-transfer-encoding:mime-version; bh=XI1swjAd+s4U/8trWw2Z16Bv4LXgWEMea5OjRur7DcA=; b=cnDUgXcvSD6REXalL4hgdvSHXX0Iyjeuic7cYbEhWXUy/JbNvueogZpX Tfah6WkxZCRWIhLgUIOdkLUfbiyRRNFt06HdjsAaeOLjbLha9iM1dVp3u iqQAmK8qVqVAjU/Aj7jnrdL/XBG8haY2CF3Xg6rWxn/I7RXlCStIw36VY E=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ag0FACxDF1StJA2J/2dsb2JhbABggw2BKgTSPQGBGhZ4hAMBAQEEOj8SAQgRAwECCxRCHQkBBA4FCIg2u04BF48cBisNgyiBHQWPN4IWoHqDXmyBSIECAQEB X-IronPort-AV: E=Sophos;i="5.04,530,1406592000"; d="scan'208";a="78152286" Received: from alln-core-4.cisco.com ([173.36.13.137]) by alln-iport-6.cisco.com with ESMTP; 15 Sep 2014 19:56:51 +0000 Received: from xhc-aln-x07.cisco.com (xhc-aln-x07.cisco.com [173.36.12.81]) by alln-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s8FJupcn008196 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 15 Sep 2014 19:56:51 GMT Received: from xmb-rcd-x13.cisco.com ([169.254.3.249]) by xhc-aln-x07.cisco.com ([173.36.12.81]) with mapi id 14.03.0195.001; Mon, 15 Sep 2014 14:56:51 -0500 From: "Siva Sivabalan (msiva)" To: "pce@ietf.org" Thread-Topic: [Pce] Adopting of draft-sivabalan-pce-segment-routing-03.txt Thread-Index: Ac/RHy8TgvmIBLhyTYq18+T2ythzCw== Date: Mon, 15 Sep 2014 19:56:51 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [161.44.212.199] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/pce/F0V2Pdxk8UV5C5pQE1aHFMjMYSo Subject: Re: [Pce] Adopting of draft-sivabalan-pce-segment-routing-03.txt X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Sep 2014 19:57:07 -0000 Support as a co-author. Thanks, Siva =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Date: Sun, 14 Sep 2014 10:06:28 +0000 From: "JP Vasseur (jvasseur)" To: "pce@ietf.org" Subject: [Pce] Adopting of draft-sivabalan-pce-segment-routing-03.txt as PCE WG Document Message-ID: Content-Type: text/plain; charset=3D"us-ascii" Dear WG, We had several discussions showing a good consensus adopting draft-sivabala= n-pce-segment-routing-03.txt and this work has considerably progressed in o= ther WG. Are you in favor of adopting draft-sivabalan-pce-segment-routing-03.txt as = a PCE WG document ? Thanks. JP and Julien. ************* From nobody Mon Sep 15 14:42:52 2014 Return-Path: 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 8C17F1A879B for ; Mon, 15 Sep 2014 14:42:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.277 X-Spam-Level: X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no 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 Al99zuWIPXOq for ; Mon, 15 Sep 2014 14:42:50 -0700 (PDT) Received: from mail-ie0-x236.google.com (mail-ie0-x236.google.com [IPv6:2607:f8b0:4001:c03::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 374C61A879F for ; Mon, 15 Sep 2014 14:42:49 -0700 (PDT) Received: by mail-ie0-f182.google.com with SMTP id tr6so5430201ieb.41 for ; Mon, 15 Sep 2014 14:42:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=9oxt+uo23ZVJZW5YYYw37RrVde24oFoyl5welGAg3HY=; b=gtaOjkEsPOjvF0yXTUo8zpSVIIRQKhhLFOR1H7ArQ6wC3V/lmkNOHSBpgsU5GjJ8l+ iOjYVcrfzXLEL/Qfwr3WwIsTe7kZ34vQ5ArsauUF9x3Y8KDP4AjJ3tEORcE2CaCrzDDv ZBHkVsyfkU7NEY9/Ah4LgL2pS2WoRYdeDEp94e/7HdEA/zksA/xmkJNz2Z8HQTS3RcJa fd3x+IP1V6HaYqtboDuD9yjpsjwzeBtEHq8Y9HffXeysUHzneLNt59yIKuANdKq+98KJ r8LgRrugS4YHjvfPBz7Kq+XMKKmDj0dmnawZ52nPndAfxiBW+E9lqC0h+rHmeYAQxqnl cFFQ== MIME-Version: 1.0 X-Received: by 10.43.0.133 with SMTP id nm5mr10661699icb.55.1410817368628; Mon, 15 Sep 2014 14:42:48 -0700 (PDT) Sender: rraszuk@gmail.com Received: by 10.107.166.8 with HTTP; Mon, 15 Sep 2014 14:42:48 -0700 (PDT) In-Reply-To: References: Date: Mon, 15 Sep 2014 23:42:48 +0200 X-Google-Sender-Auth: kfwY5e3SLjNiFwNM2crd89TeyKk Message-ID: From: Robert Raszuk To: "JP Vasseur (jvasseur)" Content-Type: multipart/alternative; boundary=bcaec50fe06319a3c005032184ba Archived-At: http://mailarchive.ietf.org/arch/msg/pce/YXBVMjDavzDBd2z1yMF7es5zqeo Cc: "pce@ietf.org" Subject: Re: [Pce] Adopting of draft-sivabalan-pce-segment-routing-03.txt as PCE WG Document X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Sep 2014 21:42:51 -0000 --bcaec50fe06319a3c005032184ba Content-Type: text/plain; charset=UTF-8 In favor (as co-author). Cheers, R. On Sun, Sep 14, 2014 at 12:06 PM, JP Vasseur (jvasseur) wrote: > Dear WG, > > We had several discussions showing a good consensus adopting > draft-sivabalan-pce-segment-routing-03.txt and this work > has considerably progressed in other WG. > > Are you in favor of adopting draft-sivabalan-pce-segment-routing-03.txt as > a PCE WG document ? > > Thanks. > > JP and Julien. > > > > > _______________________________________________ > Pce mailing list > Pce@ietf.org > https://www.ietf.org/mailman/listinfo/pce > > --bcaec50fe06319a3c005032184ba Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
In favor (as co-author).
=
Cheers,
R.

On Sun, Sep 14, 2014 at 12:06 PM, JP Vasseu= r (jvasseur) <jvasseur@cisco.com> wrote:
Dear WG,

We had several discussions showing a good consensus adopting draft-sivabala= n-pce-segment-routing-03.txt and this work
has considerably progressed in other WG.

Are you in favor of adopting draft-sivabalan-pce-segment-routing-03.txt as = a PCE WG document ?

Thanks.

JP and Julien.




_______________________________________________
Pce mailing list
Pce@ietf.org
htt= ps://www.ietf.org/mailman/listinfo/pce


--bcaec50fe06319a3c005032184ba-- From nobody Mon Sep 15 14:43:20 2014 Return-Path: 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 816451A8783 for ; Mon, 15 Sep 2014 14:43:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.277 X-Spam-Level: X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no 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 6flyUCWGW-Le for ; Mon, 15 Sep 2014 14:43:18 -0700 (PDT) Received: from mail-ie0-x22d.google.com (mail-ie0-x22d.google.com [IPv6:2607:f8b0:4001:c03::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7D1881A87B0 for ; Mon, 15 Sep 2014 14:43:11 -0700 (PDT) Received: by mail-ie0-f173.google.com with SMTP id x19so5412550ier.4 for ; Mon, 15 Sep 2014 14:43:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=euEk2FkSFjhGn0pR/SZJio4YSurh5Aa+f0d7eIKgklY=; b=LQo0Edx9ZfASBGyxleH3O7Z6zQlAa5Z9x4DOE9pGiL7o5lhPyrAAi+/vvRR/H/VS6B keWyci3xVrrHhLHzD0cwaRIgONPMKFSURQ6/9f6dJYGSulHcQtJHHTHi6i6BAHCVEV+L AygA8EumtqqOUw3Ofx5OKjegwbrrgfDWGQ98n6Bw2picIw5SxY4b8wFzFBR1Z6RyGBPX acIQCnS3MFM1hqOEY5G+YYC0XPjkIdnoXvUKKRc/6T/7jXNqD6Tly4Gy2qkSBXfmTSJO xZ8q2BKfQJjYKHNd9hW12xAdwXWORrDFFcehKZ+/HQb1PM/OYHd8lPwoA/FA0hw4B0OQ Q1OA== MIME-Version: 1.0 X-Received: by 10.50.176.202 with SMTP id ck10mr26019461igc.2.1410817390990; Mon, 15 Sep 2014 14:43:10 -0700 (PDT) Sender: rraszuk@gmail.com Received: by 10.107.166.8 with HTTP; Mon, 15 Sep 2014 14:43:10 -0700 (PDT) In-Reply-To: <70E9F53F-3A40-4CC6-924B-9BA229FD84AA@cisco.com> References: <70E9F53F-3A40-4CC6-924B-9BA229FD84AA@cisco.com> Date: Mon, 15 Sep 2014 23:43:10 +0200 X-Google-Sender-Auth: ZH3I3VGZZ1QOaIAoihMEGWGb8jM Message-ID: From: Robert Raszuk To: "JP Vasseur (jvasseur)" Content-Type: multipart/alternative; boundary=089e0111d7586edcfb0503218533 Archived-At: http://mailarchive.ietf.org/arch/msg/pce/6hry582fW_wfhTiTZEbMJCxeDRQ Cc: "pce@ietf.org" Subject: Re: [Pce] Adoption of draft-sivabalan-pce-lsp-setup-type-02.txt as a PCE WG Document X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Sep 2014 21:43:19 -0000 --089e0111d7586edcfb0503218533 Content-Type: text/plain; charset=UTF-8 Support Best, r. On Sun, Sep 14, 2014 at 12:06 PM, JP Vasseur (jvasseur) wrote: > Dear WG, > > We had several discussions showing a good consensus adopting > draft-sivabalan-pce-lsp-setup-type-02.txt and this work > has considerably progressed in other WG. > > Are you in favor of adopting draft-sivabalan-pce-lsp-setup-type-02.txt as > a PCE WG document ? > > Thanks. > > JP and Julien. > > _______________________________________________ > Pce mailing list > Pce@ietf.org > https://www.ietf.org/mailman/listinfo/pce > > --089e0111d7586edcfb0503218533 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Support=C2=A0

<= div class=3D"gmail_default" style=3D"font-family:courier new,monospace;font= -size:small">Best,
r.

On Sun, Sep 14, 2014 at 12:06 PM, JP Vas= seur (jvasseur) <jvasseur@cisco.com> wrote:
Dear WG,

We had several discussions showing a good consensus adopting draft-sivabala= n-pce-lsp-setup-type-02.txt and this work
has considerably progressed in other WG.

Are you in favor of adopting draft-sivabalan-pce-lsp-setup-type-02.txt as a= PCE WG document ?

Thanks.

JP and Julien.

_______________________________________________
Pce mailing list
Pce@ietf.org
htt= ps://www.ietf.org/mailman/listinfo/pce


--089e0111d7586edcfb0503218533-- From nobody Tue Sep 16 02:20:47 2014 Return-Path: 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 DD2C41A0208 for ; Tue, 16 Sep 2014 02:20:45 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.553 X-Spam-Level: X-Spam-Status: No, score=-3.553 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.652, 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 o1B2hUtbVowV for ; Tue, 16 Sep 2014 02:20:42 -0700 (PDT) Received: from ENFIRHETS1.metaswitch.com (enfirhets1.metaswitch.com [192.91.191.166]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9C1DE1A0202 for ; Tue, 16 Sep 2014 02:20:42 -0700 (PDT) Received: from ENFIRHMBX1.datcon.co.uk (172.18.74.36) by ENFIRHETS1.metaswitch.com (172.18.209.22) with Microsoft SMTP Server (TLS) id 14.3.195.1; Tue, 16 Sep 2014 10:20:33 +0100 Received: from ENFICSMBX1.datcon.co.uk ([fe80::d5d5:c683:a3be:3a19]) by ENFIRHMBX1.datcon.co.uk ([fe80::b06d:4d13:5f63:3715%12]) with mapi id 14.03.0195.001; Tue, 16 Sep 2014 10:20:41 +0100 From: Jonathan Hardwick To: "JP Vasseur (jvasseur)" , "pce@ietf.org" Thread-Topic: Adoption of draft-sivabalan-pce-lsp-setup-type-02.txt as a PCE WG Document Thread-Index: AQHP0AOKhQXX3FptfUeVYEz+5mQyKZwDfsnA Date: Tue, 16 Sep 2014 09:20:40 +0000 Message-ID: <09CE6C3BE5E1EA40B987BF5F25D8DDBAF4FEF410@ENFICSMBX1.datcon.co.uk> References: <70E9F53F-3A40-4CC6-924B-9BA229FD84AA@cisco.com> In-Reply-To: <70E9F53F-3A40-4CC6-924B-9BA229FD84AA@cisco.com> Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.18.10.155] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/pce/YUphIdRfGoQ8fJYp4wwP1oYoPEc Subject: Re: [Pce] Adoption of draft-sivabalan-pce-lsp-setup-type-02.txt as a PCE WG Document X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Sep 2014 09:20:46 -0000 Yes, I'm in favour of adopting this. Jon -----Original Message----- From: Pce [mailto:pce-bounces@ietf.org] On Behalf Of JP Vasseur (jvasseur) Sent: 14 September 2014 11:06 To: pce@ietf.org Subject: [Pce] Adoption of draft-sivabalan-pce-lsp-setup-type-02.txt as a P= CE WG Document Dear WG, We had several discussions showing a good consensus adopting draft-sivabala= n-pce-lsp-setup-type-02.txt and this work has considerably progressed in other WG. Are you in favor of adopting draft-sivabalan-pce-lsp-setup-type-02.txt as a= PCE WG document ? Thanks. JP and Julien. From nobody Tue Sep 16 02:21:25 2014 Return-Path: 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 9C88F1A027C for ; Tue, 16 Sep 2014 02:21:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.553 X-Spam-Level: X-Spam-Status: No, score=-3.553 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.652, 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 Zj3KxAxWa5JI for ; Tue, 16 Sep 2014 02:21:21 -0700 (PDT) Received: from ENFICSETS1.metaswitch.com (enficsets1.metaswitch.com [192.91.191.38]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4D84B1A0444 for ; Tue, 16 Sep 2014 02:21:21 -0700 (PDT) Received: from ENFIRHCAS1.datcon.co.uk (172.18.209.38) by ENFICSETS1.metaswitch.com (172.18.4.18) with Microsoft SMTP Server (TLS) id 14.3.195.1; Tue, 16 Sep 2014 10:21:15 +0100 Received: from ENFICSMBX1.datcon.co.uk ([fe80::d5d5:c683:a3be:3a19]) by ENFIRHCAS1.datcon.co.uk ([fe80::85a7:aa4e:2516:c2ad%11]) with mapi id 14.03.0195.001; Tue, 16 Sep 2014 10:21:19 +0100 From: Jonathan Hardwick To: "JP Vasseur (jvasseur)" , "pce@ietf.org" Thread-Topic: Adopting of draft-sivabalan-pce-segment-routing-03.txt as PCE WG Document Thread-Index: AQHP0AOM1KLRLywSpUW4vDYHaosXcpwDfxCg Date: Tue, 16 Sep 2014 09:21:19 +0000 Message-ID: <09CE6C3BE5E1EA40B987BF5F25D8DDBAF4FEF42D@ENFICSMBX1.datcon.co.uk> References: In-Reply-To: Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.18.10.155] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/pce/LBeS5zFoon5_cUlfFbXcdmJZ4-Y Subject: Re: [Pce] Adopting of draft-sivabalan-pce-segment-routing-03.txt as PCE WG Document X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Sep 2014 09:21:22 -0000 Yes, I'm in favour of adopting this. Jon -----Original Message----- From: Pce [mailto:pce-bounces@ietf.org] On Behalf Of JP Vasseur (jvasseur) Sent: 14 September 2014 11:06 To: pce@ietf.org Subject: [Pce] Adopting of draft-sivabalan-pce-segment-routing-03.txt as PC= E WG Document Dear WG, We had several discussions showing a good consensus adopting draft-sivabala= n-pce-segment-routing-03.txt and this work has considerably progressed in other WG. Are you in favor of adopting draft-sivabalan-pce-segment-routing-03.txt as = a PCE WG document ? Thanks. JP and Julien. From nobody Tue Sep 16 06:30:14 2014 Return-Path: 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 71FB91A0667 for ; Tue, 16 Sep 2014 06:30:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -16.153 X-Spam-Level: X-Spam-Status: No, score=-16.153 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.652, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 zZ1WXg06SD62 for ; Tue, 16 Sep 2014 06:30:12 -0700 (PDT) Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3CCB01A0704 for ; Tue, 16 Sep 2014 06:30:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=769; q=dns/txt; s=iport; t=1410874212; x=1412083812; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=VJPgPvPOiSHVzuFW15tjaDvKH+UddH+WFlcEnS0tWOA=; b=c/fBfnfSj+vASiq8LAOd3qoOTgFNHXKO5eS8k5K1iOemtK4C1WnIQkGs 3zuZMJ/RI4GUjNAJ98OpC4qMv1Vj/z2x6ua6BpVZu+5Qz+/sejXl6dzck HSSg9/p4N5ZygMIVgjRqfuigUjm9Fz9sVCr5Zju+lf8uoA/3kTOPkdwTN k=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AjUFAPc5GFStJA2M/2dsb2JhbABggw1TTQoEywwKh04BgRMWAXmEAwEBAQQBAQE3NAsMBAIBCBEEAQEfCQcnCxQJCAIEDgWIPg27QQETBI8YMwcGgyiBHQEEjzeCFos9lUSCG4FDbIFIgQIBAQE X-IronPort-AV: E=Sophos;i="5.04,534,1406592000"; d="scan'208";a="352533136" Received: from alln-core-7.cisco.com ([173.36.13.140]) by rcdn-iport-9.cisco.com with ESMTP; 16 Sep 2014 13:30:11 +0000 Received: from xhc-aln-x11.cisco.com (xhc-aln-x11.cisco.com [173.36.12.85]) by alln-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id s8GDUBt0026504 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for ; Tue, 16 Sep 2014 13:30:11 GMT Received: from xmb-rcd-x01.cisco.com ([169.254.1.160]) by xhc-aln-x11.cisco.com ([173.36.12.85]) with mapi id 14.03.0195.001; Tue, 16 Sep 2014 08:30:11 -0500 From: "Stefano Previdi (sprevidi)" To: "JP Vasseur (jvasseur)" Thread-Topic: [Pce] Adopting of draft-sivabalan-pce-segment-routing-03.txt as PCE WG Document Thread-Index: AQHP0bJW1/bkVeO7LkqChkgWJlHAQQ== Date: Tue, 16 Sep 2014 13:30:10 +0000 Message-ID: References: <09CE6C3BE5E1EA40B987BF5F25D8DDBAF4FEF42D@ENFICSMBX1.datcon.co.uk> In-Reply-To: <09CE6C3BE5E1EA40B987BF5F25D8DDBAF4FEF42D@ENFICSMBX1.datcon.co.uk> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.61.214.250] Content-Type: text/plain; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/pce/DR-T58B7nCyf9Wo8RrLNx1VvktI Cc: "pce@ietf.org" Subject: Re: [Pce] Adopting of draft-sivabalan-pce-segment-routing-03.txt as PCE WG Document X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Sep 2014 13:30:13 -0000 support. s. > -----Original Message----- > From: Pce [mailto:pce-bounces@ietf.org] On Behalf Of JP Vasseur (jvasseur= ) > Sent: 14 September 2014 11:06 > To: pce@ietf.org > Subject: [Pce] Adopting of draft-sivabalan-pce-segment-routing-03.txt as = PCE WG Document >=20 > Dear WG, >=20 > We had several discussions showing a good consensus adopting draft-sivaba= lan-pce-segment-routing-03.txt and this work > has considerably progressed in other WG. >=20 > Are you in favor of adopting draft-sivabalan-pce-segment-routing-03.txt a= s a PCE WG document ? >=20 > Thanks. >=20 > JP and Julien. >=20 >=20 >=20 > _______________________________________________ > Pce mailing list > Pce@ietf.org > https://www.ietf.org/mailman/listinfo/pce From nobody Tue Sep 16 06:30:47 2014 Return-Path: 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 F1E041A0708 for ; Tue, 16 Sep 2014 06:30:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -16.153 X-Spam-Level: X-Spam-Status: No, score=-16.153 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.652, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 o9bQwiKCb0s7 for ; Tue, 16 Sep 2014 06:30:39 -0700 (PDT) Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7B4351A0667 for ; Tue, 16 Sep 2014 06:30:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=754; q=dns/txt; s=iport; t=1410874240; x=1412083840; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=8QTcn7tQoaNW1at+fNHLxxPmsUgDoqsGrMFGUlLIkVY=; b=aAB4IRTkxvx37ZOb/eciSSc9tUmBN6oW74K0AEG2X7hfAwhCvUzwFIxv mOp5UjbBtdSPs7Mcif4FnPNtTx1HvajsrrpG10WWaM4dPcKKMtUJucjA5 Bcls0UBM27UfKEDkQ82x0cCMQa+/AUCwFziemX55joOFSPvqH2DfJc7DZ o=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AjUFAHA6GFStJA2H/2dsb2JhbABggw1TTQoEywwKh04BgRMWAXmEAwEBAQQBAQE3NAsMBAIBCBEEAQEfCQcnCxQJCAIEDgWIPg27QgETBI8YMwcGgyiBHQEEjzeCFos9lUSCG4FDbIFIgQIBAQE X-IronPort-AV: E=Sophos;i="5.04,534,1406592000"; d="scan'208";a="355604726" Received: from alln-core-2.cisco.com ([173.36.13.135]) by rcdn-iport-2.cisco.com with ESMTP; 16 Sep 2014 13:30:39 +0000 Received: from xhc-rcd-x11.cisco.com (xhc-rcd-x11.cisco.com [173.37.183.85]) by alln-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s8GDUc1I003145 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for ; Tue, 16 Sep 2014 13:30:38 GMT Received: from xmb-rcd-x01.cisco.com ([169.254.1.160]) by xhc-rcd-x11.cisco.com ([173.37.183.85]) with mapi id 14.03.0195.001; Tue, 16 Sep 2014 08:30:38 -0500 From: "Stefano Previdi (sprevidi)" To: "JP Vasseur (jvasseur)" Thread-Topic: [Pce] Adoption of draft-sivabalan-pce-lsp-setup-type-02.txt as a PCE WG Document Thread-Index: AQHP0bJnFTyKCADkBkOnHMjsffV3PA== Date: Tue, 16 Sep 2014 13:30:38 +0000 Message-ID: <8ED940EA-BBF0-4911-8F32-433B00446BA6@cisco.com> References: <70E9F53F-3A40-4CC6-924B-9BA229FD84AA@cisco.com> <09CE6C3BE5E1EA40B987BF5F25D8DDBAF4FEF410@ENFICSMBX1.datcon.co.uk> In-Reply-To: <09CE6C3BE5E1EA40B987BF5F25D8DDBAF4FEF410@ENFICSMBX1.datcon.co.uk> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.61.214.250] Content-Type: text/plain; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/pce/So6rMbVhpsMZ0AnoozPA0zQ_MGg Cc: "pce@ietf.org" Subject: Re: [Pce] Adoption of draft-sivabalan-pce-lsp-setup-type-02.txt as a PCE WG Document X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Sep 2014 13:30:44 -0000 support. s. > -----Original Message----- > From: Pce [mailto:pce-bounces@ietf.org] On Behalf Of JP Vasseur (jvasseur= ) > Sent: 14 September 2014 11:06 > To: pce@ietf.org > Subject: [Pce] Adoption of draft-sivabalan-pce-lsp-setup-type-02.txt as a= PCE WG Document >=20 > Dear WG, >=20 > We had several discussions showing a good consensus adopting draft-sivaba= lan-pce-lsp-setup-type-02.txt and this work > has considerably progressed in other WG. >=20 > Are you in favor of adopting draft-sivabalan-pce-lsp-setup-type-02.txt as= a PCE WG document ? >=20 > Thanks. >=20 > JP and Julien. >=20 > _______________________________________________ > Pce mailing list > Pce@ietf.org > https://www.ietf.org/mailman/listinfo/pce From nobody Tue Sep 16 11:06:20 2014 Return-Path: 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 42C391A6FBE for ; Tue, 16 Sep 2014 11:06:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.6 X-Spam-Level: X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 Oq2qpOufjL14 for ; Tue, 16 Sep 2014 11:06:14 -0700 (PDT) Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A7A4B1A6FD5 for ; Tue, 16 Sep 2014 11:06:13 -0700 (PDT) X-AuditID: c618062d-f79206d0000014d2-fa-541826463580 Received: from EUSAAHC003.ericsson.se (Unknown_Domain [147.117.188.81]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id 23.86.05330.64628145; Tue, 16 Sep 2014 14:00:06 +0200 (CEST) Received: from EUSAAMB105.ericsson.se ([147.117.188.122]) by EUSAAHC003.ericsson.se ([147.117.188.81]) with mapi id 14.03.0174.001; Tue, 16 Sep 2014 14:06:11 -0400 From: Uma Chunduri To: "JP Vasseur (jvasseur)" , "pce@ietf.org" Thread-Topic: [Pce] Fwd: Adopting of draft-sivabalan-pce-segment-routing-03.txt as PCE WG Document Thread-Index: AQHP0AOM1KLRLywSpUW4vDYHaosXcpwEEbtA Date: Tue, 16 Sep 2014 18:06:10 +0000 Message-ID: <1B502206DFA0C544B7A60469152008633F372E52@eusaamb105.ericsson.se> References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [147.117.188.9] Content-Type: multipart/alternative; boundary="_000_1B502206DFA0C544B7A60469152008633F372E52eusaamb105erics_" MIME-Version: 1.0 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrFLMWRmVeSWpSXmKPExsUyuXRPoK6bmkSIQfcNHYsZW94yWzTdv8Hu wOQx5fdGVo8lS34yBTBFcdmkpOZklqUW6dslcGW8ntjLXnDfoqJn9wW2BsY7Rl2MnBwSAiYS T3q6WSBsMYkL99azgdhCAkcZJeZ26kLYyxkl/lyOBbHZBPQkPk79yd7FyMEhIhAo0fg8ASQs LJAssfnuEkYQW0QgRWLqtB3MELaRxK8HLUwgNouAqsT5pvWsIDavgK/E62P9UKvyJa7Ous4O YnMK2ErMm/gd7BxGoHO+n1oD1sssIC5x68l8JogzBSSW7DnPDGGLSrx8/I8VwlaU2Nc/nR2i Pl/i8uV3bBC7BCVOznzCMoFRZBaSUbOQlM1CUgYR15FYsPsTG4StLbFs4WtmGPvMgcdMyOIL GNlXMXKUFqeW5aYbGWxiBEbOMQk23R2Me15aHmIU4GBU4uFdMFM8RIg1say4MvcQozQHi5I4 76zaecFCAumJJanZqakFqUXxRaU5qcWHGJk4OKUaGG095rq/tJHROTWrY2PkxXf3Ez3/lbp5 sbSVmazwe+mUdO7BpbDUuBvff2/9m5Waxh7A1yGUbvD7fPSyxE8lLA/MNk2ds97QvLT/0J9+ Scf2r73qIkmXlaT/rdmV+PWpf8i1pH1blf4XGn+d6lKeUPV67+aj9w02/tL8oLhmo/Ge5/Eb Uj7N3qbEUpyRaKjFXFScCACrhAL1fQIAAA== Archived-At: http://mailarchive.ietf.org/arch/msg/pce/9Ls8gl3PSGHgfk3FBtUL3RfgDbA Subject: Re: [Pce] Fwd: Adopting of draft-sivabalan-pce-segment-routing-03.txt as PCE WG Document X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Sep 2014 18:06:17 -0000 --_000_1B502206DFA0C544B7A60469152008633F372E52eusaamb105erics_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Support. -- Uma C. From: Pce [mailto:pce-bounces@ietf.org] On Behalf Of JP Vasseur (jvasseur) Sent: Sunday, September 14, 2014 6:54 AM To: pce@ietf.org Subject: [Pce] Fwd: Adopting of draft-sivabalan-pce-segment-routing-03.txt = as PCE WG Document Begin forwarded message: From: "JP Vasseur (jvasseur)" > Subject: [Pce] Adopting of draft-sivabalan-pce-segment-routing-03.txt as PC= E WG Document Date: September 14, 2014 at 12:06:28 PM GMT+2 To: "pce@ietf.org" > Dear WG, We had several discussions showing a good consensus adopting draft-sivabala= n-pce-segment-routing-03.txt and this work has considerably progressed in other WG. Are you in favor of adopting draft-sivabalan-pce-segment-routing-03.txt as = a PCE WG document ? Thanks. JP and Julien. _______________________________________________ Pce mailing list Pce@ietf.org https://www.ietf.org/mailman/listinfo/pce --_000_1B502206DFA0C544B7A60469152008633F372E52eusaamb105erics_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Support.

 <= /p>

--

Uma C.<= /p>

 <= /p>

From: Pce [mai= lto:pce-bounces@ietf.org] On Behalf Of JP Vasseur (jvasseur)
Sent: Sunday, September 14, 2014 6:54 AM
To: pce@ietf.org
Subject: [Pce] Fwd: Adopting of draft-sivabalan-pce-segment-routing-= 03.txt as PCE WG Document

 

 

 

Begin forwarded message:



From: "JP Vasseur (jvasseur)" <jvasseur@cisco.com>

Subject: [Pce] Adopting of draft-sivabalan-pce-segm= ent-routing-03.txt as PCE WG Document

Date: September 14, 2014 at 12:06:28 PM GMT+2

 

Dear WG,

We had several discussions showing a good consensus adopting draft-sivabala= n-pce-segment-routing-03.txt and this work
has considerably progressed in other WG.

Are you in favor of adopting draft-sivabalan-pce-segment-routing-03.txt as = a PCE WG document ?

Thanks.

JP and Julien.



_______________________________________________
Pce mailing list
Pce@ietf.org
https://www.ietf.org/= mailman/listinfo/pce

 

--_000_1B502206DFA0C544B7A60469152008633F372E52eusaamb105erics_-- From nobody Tue Sep 16 11:07:57 2014 Return-Path: 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 C4E251A8741 for ; Tue, 16 Sep 2014 11:07:38 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.601 X-Spam-Level: X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 LPGpy7kUEM3H for ; Tue, 16 Sep 2014 11:07:32 -0700 (PDT) Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 71C0F1A7021 for ; Tue, 16 Sep 2014 11:07:32 -0700 (PDT) X-AuditID: c618062d-f79206d0000014d2-49-54182695bf40 Received: from EUSAAHC002.ericsson.se (Unknown_Domain [147.117.188.78]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id 84.96.05330.59628145; Tue, 16 Sep 2014 14:01:26 +0200 (CEST) Received: from EUSAAMB105.ericsson.se ([147.117.188.122]) by EUSAAHC002.ericsson.se ([147.117.188.78]) with mapi id 14.03.0174.001; Tue, 16 Sep 2014 14:07:30 -0400 From: Uma Chunduri To: "JP Vasseur (jvasseur)" , "pce@ietf.org" Thread-Topic: Adoption of draft-sivabalan-pce-lsp-setup-type-02.txt as a PCE WG Document Thread-Index: AQHP0AOKhQXX3FptfUeVYEz+5mQyKZwEEfsA Date: Tue, 16 Sep 2014 18:07:30 +0000 Message-ID: <1B502206DFA0C544B7A60469152008633F372E78@eusaamb105.ericsson.se> References: <70E9F53F-3A40-4CC6-924B-9BA229FD84AA@cisco.com> In-Reply-To: <70E9F53F-3A40-4CC6-924B-9BA229FD84AA@cisco.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [147.117.188.9] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrCLMWRmVeSWpSXmKPExsUyuXSPn+40NYkQg3WzBSxmbHnLbNF0/wa7 A5PHlN8bWT2WLPnJFMAUxWWTkpqTWZZapG+XwJWxb9Ii5oI/LBWTL3ezNzC2sXQxcnJICJhI 7Hg0gxnCFpO4cG89WxcjF4eQwFFGib7DdxghnOWMEi8PTmAFqWIT0JP4OPUnexcjB4eIQKBE 4/MEkLCwQKTEyxurwEpEBKIkug72QNlGEsuerWQDsVkEVCW+fL3KBGLzCvhKNG19B3aEkICN xPqnM9lBbE4BW4nbPX/BehmBDvp+ag1YPbOAuMStJ/OZIA4VkFiy5zzU0aISLx//Y4WwFSX2 9U9nh6jXkViw+xMbhK0tsWzha2aIvYISJ2c+YZnAKDoLydhZSFpmIWmZhaRlASPLKkaO0uLU stx0I4NNjMBoOCbBpruDcc9Ly0OMAhyMSjy8C2aKhwixJpYVV+YeYpTmYFES551VOy9YSCA9 sSQ1OzW1ILUovqg0J7X4ECMTB6dUA6OnzqpTfm6tWlwxrgrqasGas8sXBEnonai83J6S4pGQ IbHvvNndhbbcM578L7ruI/fI0fTZO91bl6rlDv84slpRf3X+jhir4FVynLa+4T2hU1sMTv2z c5sVaWX6b5onY9IKcRWnlk+5GVuWmth2zTl9cuqbCp8/sfNt/u1Wcr22N2bDE9/ePUosxRmJ hlrMRcWJAJvqkOpnAgAA Archived-At: http://mailarchive.ietf.org/arch/msg/pce/2MQkKbFqoa2mE4kX04_usl2Otgk Subject: Re: [Pce] Adoption of draft-sivabalan-pce-lsp-setup-type-02.txt as a PCE WG Document X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Sep 2014 18:07:39 -0000 Yes/Support. Have comments and will send later. -- Uma C. -----Original Message----- From: Pce [mailto:pce-bounces@ietf.org] On Behalf Of JP Vasseur (jvasseur) Sent: Sunday, September 14, 2014 3:06 AM To: pce@ietf.org Subject: [Pce] Adoption of draft-sivabalan-pce-lsp-setup-type-02.txt as a P= CE WG Document Dear WG, We had several discussions showing a good consensus adopting draft-sivabala= n-pce-lsp-setup-type-02.txt and this work has considerably progressed in ot= her WG. Are you in favor of adopting draft-sivabalan-pce-lsp-setup-type-02.txt as a= PCE WG document ? Thanks. JP and Julien. From nobody Wed Sep 17 02:19:21 2014 Return-Path: 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 86CA01A0089 for ; Wed, 17 Sep 2014 02:19:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.853 X-Spam-Level: X-Spam-Status: No, score=-5.853 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-1.652, 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 SS1X4RN5mMQC for ; Wed, 17 Sep 2014 02:19:17 -0700 (PDT) Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A58CD1A0081 for ; Wed, 17 Sep 2014 02:19:16 -0700 (PDT) Received: from 172.18.7.190 (EHLO lhreml405-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BMR86696; Wed, 17 Sep 2014 09:19:15 +0000 (GMT) Received: from SZXEML449-HUB.china.huawei.com (10.82.67.192) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 17 Sep 2014 10:19:13 +0100 Received: from szxeml556-mbs.china.huawei.com ([169.254.4.112]) by szxeml449-hub.china.huawei.com ([10.82.67.192]) with mapi id 14.03.0158.001; Wed, 17 Sep 2014 17:18:47 +0800 From: Dhruv Dhody To: "JP Vasseur (jvasseur)" , "pce@ietf.org" Thread-Topic: Adopting of draft-sivabalan-pce-segment-routing-03.txt as PCE WG Document Thread-Index: AQHP0AOM1KLRLywSpUW4vDYHaosXcpwEoo8w Date: Wed, 17 Sep 2014 09:18:46 +0000 Message-ID: <23CE718903A838468A8B325B80962F9B865F86FC@szxeml556-mbs.china.huawei.com> References: In-Reply-To: Accept-Language: en-GB, zh-CN, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.18.146.248] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-CFilter-Loop: Reflected Archived-At: http://mailarchive.ietf.org/arch/msg/pce/iClPhxP8QbqeyjGf85YLhvsP1K0 Subject: Re: [Pce] Adopting of draft-sivabalan-pce-segment-routing-03.txt as PCE WG Document X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Sep 2014 09:19:19 -0000 Support, have following suggestions... Sec 1. Introduction =20 A PCE or a PCC operating as a PCE (in hierarchical PCE environment) computes paths for MPLS Traffic Engineering LSPs (MPLS-TE LSPs) based on various constraints and optimization criteria. I find 'PCC operating as a PCE' confusing here, it doesn't add any value, p= erhaps you could say "A PCE or a set of cooperating PCEs compute ...." Sec 3. Overview of PCEP Operation in SR Networks =20 o An ordered set of both MPLS label(s) and IP address(es): In this case, the PCC needs to convert the IP address(es) into the corresponding SID(s) by consulting its TED. Do you mean a combination of label and corresponding IP address? Or some no= des and links are represented as Labels and some with IP address? The descr= iption seems to suggest the latter in which case it might be stated more cl= early.=20 Furthermore, an LSP initially established via RSVP-TE signaling can be updated with SR-TE path. This capability is useful when a network is migrated from RSVP-TE to SR-TE technology. Similarly, an LSP initially created with SR-TE path can updated to signal the LSP using RSVP-TE if necessary. The procedure to do so should be stated, the Path Setup Type TLV with the n= ew PST seems like an obvious solution, maybe this could be placed in draft-= sivabalan-pce-lsp-setup-type as a generic mechanism.=20 The extensions specified in this document are applicable to the stateless PCE model defined in [RFC5440], as well as for the active stateful and passive stateful PCE models defined in [I-D.ietf-pce-stateful-pce]. [I-D.ietf-pce-pce-initiated-lsp] can be added to this list as well.=20 The SR Capability TLV is meaningful only in the OPEN message sent from a PCC to a PCE. =20 I think you mean the MSD value inside the SR capability TLV and not the ful= l TLV itself? Sec 5.3. ERO Object Note that an SR-ERO subobject does not need to have both SID and NAI. However, at least one of them MUST be present. To handle this case you suggest... 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |L| Type | Length | ST | Flags |F|S|C|M| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | SID | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ // NAI (variable) // +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ SR-ERO subobject may have only SID, only NAI or both, and you list the vari= ous combination of length possible for each ST type.=20 The figure above doesn't reflect that, as SID looks permanent.=20 Moreover, can the encoding be simplified by making SID encoding a must (as = shown in the figure in the draft) with a suitable NULL value reserved for t= he case when SID is not present or simply the value is ignored when S flag = is set.=20 Nits - Expand LDP, RSVP-TE on first use - Update reference filsfils-rtgwg-segment-routing to draft-filsfils-spring-= segment-routing - SID Type (ST) can be listed independently and not clubbed with NAI descri= ption in section 5.3.1 Hope the authors and WG find these useful. Regards, Dhruv > -----Original Message----- > From: Pce [mailto:pce-bounces@ietf.org] On Behalf Of JP Vasseur (jvasseur= ) > Sent: 14 September 2014 18:06 > To: pce@ietf.org > Subject: [Pce] Adopting of draft-sivabalan-pce-segment-routing-03.txt as = PCE > WG Document >=20 > Dear WG, >=20 > We had several discussions showing a good consensus adopting draft-sivaba= lan- > pce-segment-routing-03.txt and this work has considerably progressed in o= ther > WG. >=20 > Are you in favor of adopting draft-sivabalan-pce-segment-routing-03.txt a= s a > PCE WG document ? >=20 > Thanks. >=20 > JP and Julien. >=20 >=20 From nobody Wed Sep 17 02:19:53 2014 Return-Path: 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 DEFD11A0040 for ; Wed, 17 Sep 2014 02:19:49 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.853 X-Spam-Level: X-Spam-Status: No, score=-5.853 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-1.652, 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 OoHo_eSlX277 for ; Wed, 17 Sep 2014 02:19:47 -0700 (PDT) Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CE7291A00F5 for ; Wed, 17 Sep 2014 02:19:42 -0700 (PDT) Received: from 172.18.7.190 (EHLO lhreml403-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BMR86743; Wed, 17 Sep 2014 09:19:41 +0000 (GMT) Received: from SZXEML422-HUB.china.huawei.com (10.82.67.161) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 17 Sep 2014 10:19:40 +0100 Received: from szxeml556-mbs.china.huawei.com ([169.254.4.112]) by szxeml422-hub.china.huawei.com ([10.82.67.161]) with mapi id 14.03.0158.001; Wed, 17 Sep 2014 17:19:34 +0800 From: Dhruv Dhody To: "JP Vasseur (jvasseur)" , "pce@ietf.org" Thread-Topic: Adoption of draft-sivabalan-pce-lsp-setup-type-02.txt as a PCE WG Document Thread-Index: AQHP0AOKhQXX3FptfUeVYEz+5mQyKZwEl1vA Date: Wed, 17 Sep 2014 09:19:34 +0000 Message-ID: <23CE718903A838468A8B325B80962F9B865F8709@szxeml556-mbs.china.huawei.com> References: <70E9F53F-3A40-4CC6-924B-9BA229FD84AA@cisco.com> In-Reply-To: <70E9F53F-3A40-4CC6-924B-9BA229FD84AA@cisco.com> Accept-Language: en-GB, zh-CN, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.18.146.248] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-CFilter-Loop: Reflected Archived-At: http://mailarchive.ietf.org/arch/msg/pce/Cj-UyNozD12YpVqzkj-ve29z6aA Subject: Re: [Pce] Adoption of draft-sivabalan-pce-lsp-setup-type-02.txt as a PCE WG Document X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Sep 2014 09:19:50 -0000 Support, have following suggestions.=20 Sec 3. Path Setup Type TLV =20 The one octet value contains the Path Setup Type (PST). This document specifies the following PST value: o PST =3D 0: Path is setup via RSVP-TE signaling protocol(default). Can some PST value be reserved for experimental or private use for future e= xperiments? =20 If a PCEP speaker does not recognize the PATH-SETUP-TYPE TLV, it MUST ignore the TLV in accordance with ([RFC5440]). =20 Along with the unrecognizable TLV type, we should also state the behavior f= or unrecognized PST value (for future documents that define new PST). It is= better if this is uniform across PST and defined in this document itself.= =20 Sec 4. Operation Regardless of whether PATH-SETUP-TYPE TLV is used or not, if the PCE does not support the intended path setup type it MUST send PCErr with Error-Type =3D TBD (Traffic engineering path setup error) (recommended value is 21) and Error-Value =3D 1 (Unsupported path setup type) and close the PCEP session. On the first read closing the session seems harsh, but since open message M= UST exchange the capability of supporting new path setup type, this seems f= ine. Maybe a few lines to explain the rationale can be added. Something in = line of...=20 "Before using the PATH-SETUP-TYPE (other than default), the PCEP speaker MUST notify the capability to support the new path setup type during=20 the session establishment phase. Only if both PCEP peers support the capability the PATH-SETUP-TYPE TLV with new PST be used. " =20 Editorial Nits - Expand RSVP-TE, PCEP on first use in abstract=20 Hope the authors find these useful. Regards, Dhruv > -----Original Message----- > From: Pce [mailto:pce-bounces@ietf.org] On Behalf Of JP Vasseur (jvasseur= ) > Sent: 14 September 2014 18:06 > To: pce@ietf.org > Subject: [Pce] Adoption of draft-sivabalan-pce-lsp-setup-type-02.txt as a= PCE > WG Document >=20 > Dear WG, >=20 > We had several discussions showing a good consensus adopting draft-sivaba= lan- > pce-lsp-setup-type-02.txt and this work has considerably progressed in ot= her > WG. >=20 > Are you in favor of adopting draft-sivabalan-pce-lsp-setup-type-02.txt as= a > PCE WG document ? >=20 > Thanks. >=20 > JP and Julien. From nobody Wed Sep 17 07:44:11 2014 Return-Path: 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 79A791A04A6 for ; Wed, 17 Sep 2014 07:44:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.652 X-Spam-Level: X-Spam-Status: No, score=-3.652 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, RP_MATCHES_RCVD=-1.652, 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 DIyItDOijfoO for ; Wed, 17 Sep 2014 07:44:06 -0700 (PDT) Received: from nm28-vm4.bullet.mail.gq1.yahoo.com (nm28-vm4.bullet.mail.gq1.yahoo.com [98.136.216.163]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9CDD31A048D for ; Wed, 17 Sep 2014 07:44:06 -0700 (PDT) Received: from [98.137.12.58] by nm28.bullet.mail.gq1.yahoo.com with NNFMP; 17 Sep 2014 14:44:06 -0000 Received: from [98.137.12.244] by tm3.bullet.mail.gq1.yahoo.com with NNFMP; 17 Sep 2014 14:44:06 -0000 Received: from [127.0.0.1] by omp1052.mail.gq1.yahoo.com with NNFMP; 17 Sep 2014 14:44:06 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 354378.88279.bm@omp1052.mail.gq1.yahoo.com Received: (qmail 97378 invoked by uid 60001); 17 Sep 2014 14:44:06 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1410965046; bh=g5WC2nkrWuVJ7cXZR56AEBORsUFCSUiLyoZ1aaQDUVs=; h=Message-ID:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=DHaRAH7yJr54MXcdRzeQyn1489TY1d/o1XEGDXqIRhlmxVi5NDq1eHp9g5nunPhAJDzSXeQ4i5GihavIB6kccIonuZ+rt3OvQOCwe/PzwxQg364wxKX5aCsfl8BaB5/8oK8kpByB79O4UhU7tCrX6XxdFUfrEWQfhIJkSdhy2Lk= X-YMail-OSG: Rh8mNWsVM1k6C51ghSKKrJQ4AyodqadJy4.n3s39t2qtwg5 eY031pYb34NycTY.mFdI1.L4AszhQ2JiczaDqWmVqeZFmdNNfKx_35xAEE_T .hYcpQHvrbWsE9UFZkYnI1OXpr7dDCugpF1SsJ4m4TVC2TLUksRN9MGzRh_3 5qCb0qouWBRAKYCj.io7PIGHCyE2zd5rR9pn3oyr6od91YG07L7CHaG8eBeF uEJAlcN6QIDSbeer4j5T21YXvceUakuzMFRe4f0pKr5tmRKqM_jjATtMmMJ4 gXOVWrO5gx6vCi3ARS1ZzmfDm4kNBwzBrbnCeXNkW4MZPXmHAn9tBwidup8H kZvLz3moLfQ7O5__zP8uTUgAukVPkfIVS2IkyqLxyZNEFokzDoHRtoDv9BCR w4e1X8e6LuRAF5jeZLYP.lBG8s32fvHAI4oJRcVJvWeB9XyrHhKJ.S6hLG25 EamqP.l.BWhrcTJCZ1kOuaut8l8iwJDhB6D.f1lJEzK8n7pH6SDcG5SokW_2 9tRVcmbSXurQpNWmG7rY1JOAtWPVllWPwmUvdRSUG_fjMJcK1xu.K5o2C Received: from [148.184.174.62] by web164801.mail.gq1.yahoo.com via HTTP; Wed, 17 Sep 2014 07:44:06 PDT X-Rocket-MIMEInfo: 002.001, U3VwcG9ydC4NCg0KDQpCcmdkcyxERw0KIsKgSSd2ZcKgaGFkwqBnb29kIHNlYXNvbnMgYW5kIHNvbWUgZGVlcGx5wqBwYWluZnVsIG9uZXMuwqBJJ3ZlwqBtYWRlwqBzb21lIHNwZWN0YWN1bGFybHnCoGdvb2QgY2hvaWNlcyBhbmTCoHNvbWXCoG91dHJhZ2VvdXNseSBiYWQgbWlzdGFrZXMuIEknbcKgdmVyecKgaHVtYW4gLSBhIHdvcmsgaW4gcHJvZ3Jlc3MiLiDCoC0gUm9iaW4gU2hhcm1hDQp.fn5.fn5.fn5.fn5.fn5.fn5.fn5.fn5.fn5.fn5.fn5.fn5.fn5.fn5.fn5.fn5.wqANCg0KLS0tLS0tLS0tLS0BMAEBAQE- X-Mailer: YahooMailClassic/735 YahooMailWebService/0.8.203.696 Message-ID: <1410965046.28262.YahooMailBasic@web164801.mail.gq1.yahoo.com> Date: Wed, 17 Sep 2014 07:44:06 -0700 From: Durgaprasad Gangisetti To: "JP Vasseur \(jvasseur\)" , "pce@ietf.org" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Archived-At: http://mailarchive.ietf.org/arch/msg/pce/M6A_dlYF5yGz5aABQFFdKQgF7Tc Subject: Re: [Pce] Adoption of draft-sivabalan-pce-lsp-setup-type-02.txt as a PCE WG Document X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Sep 2014 14:44:08 -0000 Support. Brgds,DG "=C2=A0I've=C2=A0had=C2=A0good seasons and some deeply=C2=A0painful ones.= =C2=A0I've=C2=A0made=C2=A0some spectacularly=C2=A0good choices and=C2=A0som= e=C2=A0outrageously bad mistakes. I'm=C2=A0very=C2=A0human - a work in prog= ress". =C2=A0- Robin Sharma ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~=C2=A0 -------------------------------------------- On Mon, 9/15/14, Zafar Ali (zali) wrote: Subject: Re: [Pce] Adoption of draft-sivabalan-pce-lsp-setup-type-02.txt a= s a PCE WG Document To: "JP Vasseur (jvasseur)" , "pce@ietf.org" Date: Monday, September 15, 2014, 12:17 AM =20 Support! =20 Thanks =20 Regards =C5=A0 Zafar =20 =20 =20 -----Original Message----- From: "JP Vasseur=C2=A0=C2=A0=C2=A0(jvasseur)" Date: Sunday, September 14, 2014 6:06 AM To: "pce@ietf.org" Subject: [Pce] Adoption of draft-sivabalan-pce-lsp-setup-type-02.txt as a PCE WG Document =20 >Dear WG, > >We had several discussions showing a good consensus adopting >draft-sivabalan-pce-lsp-setup-type-02.txt and this work >has considerably progressed in other WG. > >Are you in favor of adopting draft-sivabalan-pce-lsp-setup-type-02.txt as >a PCE WG document ? > >Thanks. > >JP and Julien. =20 _______________________________________________ Pce mailing list Pce@ietf.org https://www.ietf.org/mailman/listinfo/pce From nobody Wed Sep 17 08:01:41 2014 Return-Path: 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 A5EF31A0654 for ; Wed, 17 Sep 2014 08:01:38 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.902 X-Spam-Level: X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-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 SmQvmNtMYxFg for ; Wed, 17 Sep 2014 08:01:34 -0700 (PDT) Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2on0143.outbound.protection.outlook.com [65.55.169.143]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AF5C71A0194 for ; Wed, 17 Sep 2014 08:01:33 -0700 (PDT) Received: from BN1PR05MB358.namprd05.prod.outlook.com (10.141.61.147) by BN1PR05MB360.namprd05.prod.outlook.com (10.141.61.153) with Microsoft SMTP Server (TLS) id 15.0.1029.13; Wed, 17 Sep 2014 15:01:31 +0000 Received: from BN1PR05MB358.namprd05.prod.outlook.com ([169.254.2.241]) by BN1PR05MB358.namprd05.prod.outlook.com ([169.254.2.149]) with mapi id 15.00.1029.000; Wed, 17 Sep 2014 15:01:31 +0000 From: Ramana Yarlagadda To: "pce@ietf.org" Thread-Topic: minor discrepancy of Flags definition Thread-Index: AQHP0ohDXv0lJjQul0ClLJ5QKCNwlg== Date: Wed, 17 Sep 2014 15:01:30 +0000 Message-ID: <8ed250570d734ce48d2afd971231dc1c@BN1PR05MB358.namprd05.prod.outlook.com> References: <70E9F53F-3A40-4CC6-924B-9BA229FD84AA@cisco.com> <23CE718903A838468A8B325B80962F9B865F8709@szxeml556-mbs.china.huawei.com> In-Reply-To: <23CE718903A838468A8B325B80962F9B865F8709@szxeml556-mbs.china.huawei.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [66.129.239.13] x-microsoft-antispam: BCL:0;PCL:0;RULEID:;UriScan:; x-forefront-prvs: 0337AFFE9A x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(189002)(199003)(108616004)(50986999)(229853001)(4396001)(110136001)(33646002)(107046002)(2656002)(85306004)(105586002)(92566001)(54356999)(66066001)(85852003)(87936001)(99396002)(83322001)(83072002)(106116001)(2351001)(101416001)(97736003)(64706001)(77982003)(46102003)(74662003)(21056001)(74316001)(76176999)(81342003)(86362001)(106356001)(76482002)(99286002)(95666004)(20776003)(2501002)(74502003)(76576001)(79102003)(80022003)(31966008)(107886001)(81542003)(90102001)(77096002)(24736002); DIR:OUT; SFP:1102; SCL:1; SRVR:BN1PR05MB360; H:BN1PR05MB358.namprd05.prod.outlook.com; FPR:; MLV:sfv; PTR:InfoNoRecords; MX:1; A:1; LANG:en; Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: juniper.net Archived-At: http://mailarchive.ietf.org/arch/msg/pce/gTQwl6a1MeqRqccBUSzUmaKW6oA Subject: [Pce] minor discrepancy of Flags definition X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Sep 2014 15:01:38 -0000 Hi, A noticed a minor discrepancy of Flags definition between the draft-ietf-pc= e-pce-initiated-lsp-01 And ietf-pce-stateful-pce Referring sec 5.3.1 of pce-pce-initiated-lsp-01, following is the definitio= n of Create flag. And has Only two bits assigned for operational state.=20 But the definition of the Flags has 3 bits for operational state in section= 7.3. of ietf-pce-stateful-pce. 5.3.1. The Create flag The LSP object is defined in [I-D.ietf-pce-stateful-pce] and included here for easy reference. 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | PLSP-ID | Flags |C| O|A|R|S|D| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ // TLVs // | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ -regards -ramana From nobody Wed Sep 17 19:43:46 2014 Return-Path: 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 A187E1A006F for ; Wed, 17 Sep 2014 19:43:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.9 X-Spam-Level: X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, USER_IN_WHITELIST=-100] 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 v2qJXFlIGlI0 for ; Wed, 17 Sep 2014 19:43:30 -0700 (PDT) Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 53B4D1A0099 for ; Wed, 17 Sep 2014 19:43:30 -0700 (PDT) Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id s8I2hQ3h030945; Thu, 18 Sep 2014 03:43:26 +0100 Received: from 950129200 (176-227-128-84.ip.skylogicnet.com [176.227.128.84]) (authenticated bits=0) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id s8I2hFDR030842 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 18 Sep 2014 03:43:22 +0100 From: "Adrian Farrel" To: Date: Thu, 18 Sep 2014 03:43:12 +0100 Message-ID: <033001cfd2ea$507eef30$f17ccd90$@olddog.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 14.0 Thread-Index: Ac/S6fLxSQSIQaOISi+Ey3mIlZ9+LA== Content-Language: en-gb X-TM-AS-MML: disable X-TM-AS-Product-Ver: IMSS-7.1.0.1576-7.5.0.1018-20960.002 X-TM-AS-Result: No--2.866-10.0-31-10 X-imss-scan-details: No--2.866-10.0-31-10 X-TMASE-MatchedRID: SfLIqAdrccWf9SROPcS9xtxajlW+zwxCh8Ytn75ClDMhXy0Vy8CS1LZV h39LD7EPZWgNdukQjzwXFmzRp68V66jzS7OMxwt5SEQN/D/3cG7j5lyuq8IOQci9AjK6C8p1EoB 7CD3tV5j1GUSzhrwwMppJOGoBFQ8cOlcsoX/uQ8hrDUnWABcnUiTbbsi+pqSF1JVSTP0E9d7UdS C3YqYARyEn+59qml4SkZOl7WKIImq0P2qkGU0XygtuKBGekqUpnH7sbImOEBQNnKx5HmpwRQFg/ qxzRKvtgtbXa4OudqpeODEmR4yp2Sc4SDL0q8PzHaCuu9eoDuividoQ0eEoFYeCQkXxOcd7ATt9 0Ubj4yjkP2yapUEP3KKWedUMQI938fsC+xPFkxvsNp90fT4EjrAUyUg9ogFt Archived-At: http://mailarchive.ietf.org/arch/msg/pce/s_HqcUQKAQ7g8eB7f40bJCYKiew Cc: pce-chairs@tools.ietf.org Subject: [Pce] Preaching about code points in drafts X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: adrian@olddog.co.uk List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Sep 2014 02:43:37 -0000 PCE working group, draft-ietf-pce-rfc7150bis is fixing a clash between an IANA allocation for RFC 7150 and an unallocated code point documented in a working group Internet-Draft that had been picked up and used by multiple implementations. Another clash has just been pointed out to me between RFC 7150 and draft-ietf-pce-gmpls-pcep-extensions. The specifying of unallocated values in PCE I-Ds has got to stop before significant clashes happen in the field. Cease! Desist! It is not necessary, and there is a simple solution to get code points if you need them. Steps to be followed: 1. Identify all I-Ds that state or recommend values for code points (see below). 2. Decide whether the values shown are needed to support existing implementations. 2a. If so, make an immediate request to the WG chairs for early allocation of the code points using the procedures of RFC 7120. 2b. If not, make an immediate revision of the I-D removing the specific code point values. 3. In the future, when implementations of an I-D become advanced enough to be close shipping or starting interop testing, use RFC 7120 to get code points allocated. 4. Do not adopt any I-D as a working group draft if it specifies code points. Current drafts draft-ietf-pce-pce-initiated-lsp specifies unallocated values draft-ietf-pce-pcep-stateful-pce-gmpls suggests values draft-ietf-pce-remote-initiated-gmpls-lsp specifies an unallocated value draft-ietf-pce-stateful-pce suggests multiple unallocated values draft-ietf-pce-stateful-sync-optimizations specifies and suggests multiple unallocated values Recently-expired drafts draft-ietf-pce-gmpls-pcep-extensions specifies multiple unallocated values draft-ietf-pce-inter-layer-ext recommends multiple unallocated values Thanks, Adrian From nobody Thu Sep 18 01:32:02 2014 Return-Path: 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 E7DC11A03E8 for ; Thu, 18 Sep 2014 01:32:01 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.853 X-Spam-Level: X-Spam-Status: No, score=-5.853 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-1.652, 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 cvo0AFZbZD1A for ; Thu, 18 Sep 2014 01:32:00 -0700 (PDT) Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DAC5B1A0029 for ; Thu, 18 Sep 2014 01:31:59 -0700 (PDT) Received: from 172.18.7.190 (EHLO lhreml406-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BJO80772; Thu, 18 Sep 2014 08:31:58 +0000 (GMT) Received: from SZXEMA402-HUB.china.huawei.com (10.82.72.34) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 18 Sep 2014 09:31:57 +0100 Received: from SZXEMA504-MBS.china.huawei.com ([169.254.8.123]) by SZXEMA402-HUB.china.huawei.com ([10.82.72.34]) with mapi id 14.03.0158.001; Thu, 18 Sep 2014 16:31:52 +0800 From: Fatai Zhang To: "adrian@olddog.co.uk" , "pce@ietf.org" Thread-Topic: [Pce] Preaching about code points in drafts Thread-Index: Ac/S6fLxSQSIQaOISi+Ey3mIlZ9+LAALzfkg Date: Thu, 18 Sep 2014 08:31:51 +0000 Message-ID: References: <033001cfd2ea$507eef30$f17ccd90$@olddog.co.uk> In-Reply-To: <033001cfd2ea$507eef30$f17ccd90$@olddog.co.uk> Accept-Language: zh-CN, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.66.72.159] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-CFilter-Loop: Reflected Archived-At: http://mailarchive.ietf.org/arch/msg/pce/wkUyE5S5JpKH8BdqBJkDZEbeJO0 Cc: "pce-chairs@tools.ietf.org" Subject: Re: [Pce] Preaching about code points in drafts X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Sep 2014 08:32:02 -0000 Hi Adrian, I think the steps you proposed really make sense.=20 I have one comment for clarification on step (2a) and (4), did you mean tha= t it only needs to use "TBD" rather than the suggested values?=20 In addtion, for the new drafts (or non-existing drafts with clash), can I r= e-order your steps as follows? :-) 1. Do not adopt any I-D as a working group draft if it specifies code point= s. 2. In the future, when implementations of an I-D become advanced enough to = be close shipping or starting interop testing, use RFC 7120 to get code poi= nts allocated. Best Regards Fatai -----Original Message----- From: Pce [mailto:pce-bounces@ietf.org] On Behalf Of Adrian Farrel Sent: Thursday, September 18, 2014 10:43 AM To: pce@ietf.org Cc: pce-chairs@tools.ietf.org Subject: [Pce] Preaching about code points in drafts PCE working group, draft-ietf-pce-rfc7150bis is fixing a clash between an IANA allocation for = RFC 7150 and an unallocated code point documented in a working group Internet-D= raft that had been picked up and used by multiple implementations. Another clash has just been pointed out to me between RFC 7150 and draft-ietf-pce-gmpls-pcep-extensions. The specifying of unallocated values in PCE I-Ds has got to stop before significant clashes happen in the field. Cease! Desist! It is not necessary= , and there is a simple solution to get code points if you need them. Steps to be followed: 1. Identify all I-Ds that state or recommend values for code points (see be= low). 2. Decide whether the values shown are needed to support existing implementations. 2a. If so, make an immediate request to the WG chairs for early allocation = of the code points using the procedures of RFC 7120. 2b. If not, make an immediate revision of the I-D removing the specific cod= e point values. 3. In the future, when implementations of an I-D become advanced enough to = be close shipping or starting interop testing, use RFC 7120 to get code points allocated. 4. Do not adopt any I-D as a working group draft if it specifies code point= s. Current drafts draft-ietf-pce-pce-initiated-lsp specifies unallocated values draft-ietf-pce-pcep-stateful-pce-gmpls suggests values draft-ietf-pce-remote-initiated-gmpls-lsp specifies an unallocated value draft-ietf-pce-stateful-pce suggests multiple unallocated values draft-ietf-pce-stateful-sync-optimizations specifies and suggests multiple unallocated values Recently-expired drafts draft-ietf-pce-gmpls-pcep-extensions specifies multiple unallocated values draft-ietf-pce-inter-layer-ext recommends multiple unallocated values Thanks, Adrian _______________________________________________ Pce mailing list Pce@ietf.org https://www.ietf.org/mailman/listinfo/pce From nobody Thu Sep 18 01:53:56 2014 Return-Path: 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 EF3101A03F0 for ; Thu, 18 Sep 2014 01:53:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.853 X-Spam-Level: X-Spam-Status: No, score=-5.853 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-1.652, 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 CHfl_dKMktaj for ; Thu, 18 Sep 2014 01:53:51 -0700 (PDT) Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C0BED1A0029 for ; Thu, 18 Sep 2014 01:53:50 -0700 (PDT) Received: from 172.18.7.190 (EHLO lhreml403-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BJO83304; Thu, 18 Sep 2014 08:53:49 +0000 (GMT) Received: from SZXEMA406-HUB.china.huawei.com (10.82.72.38) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 18 Sep 2014 09:53:48 +0100 Received: from SZXEMA504-MBS.china.huawei.com ([169.254.8.123]) by SZXEMA406-HUB.china.huawei.com ([10.82.72.38]) with mapi id 14.03.0158.001; Thu, 18 Sep 2014 16:53:43 +0800 From: Fatai Zhang To: "adrian@olddog.co.uk" , "pce@ietf.org" Thread-Topic: [Pce] Preaching about code points in drafts Thread-Index: Ac/S6fLxSQSIQaOISi+Ey3mIlZ9+LAALzfkgAAEx46A= Date: Thu, 18 Sep 2014 08:53:43 +0000 Message-ID: References: <033001cfd2ea$507eef30$f17ccd90$@olddog.co.uk> Accept-Language: zh-CN, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.66.72.159] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-CFilter-Loop: Reflected Archived-At: http://mailarchive.ietf.org/arch/msg/pce/NaBFrVfOLlILUPyM44L-_2GJuV4 Cc: "pce-chairs@tools.ietf.org" Subject: Re: [Pce] Preaching about code points in drafts X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Sep 2014 08:53:53 -0000 Hi,=20 Sorry, I should say (2b) and (4), :-) Best Regards Fatai -----Original Message----- From: Fatai Zhang=20 Sent: Thursday, September 18, 2014 4:32 PM To: 'adrian@olddog.co.uk'; pce@ietf.org Cc: pce-chairs@tools.ietf.org Subject: RE: [Pce] Preaching about code points in drafts Hi Adrian, I think the steps you proposed really make sense.=20 I have one comment for clarification on step (2a) and (4), did you mean tha= t it only needs to use "TBD" rather than the suggested values?=20 In addtion, for the new drafts (or non-existing drafts with clash), can I r= e-order your steps as follows? :-) 1. Do not adopt any I-D as a working group draft if it specifies code point= s. 2. In the future, when implementations of an I-D become advanced enough to = be close shipping or starting interop testing, use RFC 7120 to get code poi= nts allocated. Best Regards Fatai -----Original Message----- From: Pce [mailto:pce-bounces@ietf.org] On Behalf Of Adrian Farrel Sent: Thursday, September 18, 2014 10:43 AM To: pce@ietf.org Cc: pce-chairs@tools.ietf.org Subject: [Pce] Preaching about code points in drafts PCE working group, draft-ietf-pce-rfc7150bis is fixing a clash between an IANA allocation for = RFC 7150 and an unallocated code point documented in a working group Internet-D= raft that had been picked up and used by multiple implementations. Another clash has just been pointed out to me between RFC 7150 and draft-ietf-pce-gmpls-pcep-extensions. The specifying of unallocated values in PCE I-Ds has got to stop before significant clashes happen in the field. Cease! Desist! It is not necessary= , and there is a simple solution to get code points if you need them. Steps to be followed: 1. Identify all I-Ds that state or recommend values for code points (see be= low). 2. Decide whether the values shown are needed to support existing implementations. 2a. If so, make an immediate request to the WG chairs for early allocation = of the code points using the procedures of RFC 7120. 2b. If not, make an immediate revision of the I-D removing the specific cod= e point values. 3. In the future, when implementations of an I-D become advanced enough to = be close shipping or starting interop testing, use RFC 7120 to get code points allocated. 4. Do not adopt any I-D as a working group draft if it specifies code point= s. Current drafts draft-ietf-pce-pce-initiated-lsp specifies unallocated values draft-ietf-pce-pcep-stateful-pce-gmpls suggests values draft-ietf-pce-remote-initiated-gmpls-lsp specifies an unallocated value draft-ietf-pce-stateful-pce suggests multiple unallocated values draft-ietf-pce-stateful-sync-optimizations specifies and suggests multiple unallocated values Recently-expired drafts draft-ietf-pce-gmpls-pcep-extensions specifies multiple unallocated values draft-ietf-pce-inter-layer-ext recommends multiple unallocated values Thanks, Adrian _______________________________________________ Pce mailing list Pce@ietf.org https://www.ietf.org/mailman/listinfo/pce From nobody Thu Sep 18 04:06:18 2014 Return-Path: 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 AF54F1A8779 for ; Thu, 18 Sep 2014 04:06:14 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.552 X-Spam-Level: X-Spam-Status: No, score=-3.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.652] 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 W4aGutNOuf5U for ; Thu, 18 Sep 2014 04:06:11 -0700 (PDT) Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0E0D91A876C for ; Thu, 18 Sep 2014 04:05:59 -0700 (PDT) Received: from [192.168.0.106] (81-229-83-119-no65.business.telia.com [81.229.83.119]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id 327DE180131A; Thu, 18 Sep 2014 13:05:58 +0200 (CEST) Message-ID: <541ABC98.5050200@pi.nu> Date: Thu, 18 Sep 2014 13:06:00 +0200 From: Loa Andersson User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Fatai Zhang , "adrian@olddog.co.uk" , "pce@ietf.org" References: <033001cfd2ea$507eef30$f17ccd90$@olddog.co.uk> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Archived-At: http://mailarchive.ietf.org/arch/msg/pce/fA_rEViqCb2Cff7L9My-jJZckts Cc: "pce-chairs@tools.ietf.org" Subject: Re: [Pce] Preaching about code points in drafts X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Sep 2014 11:06:15 -0000 Fatai, I agree with you - I also don't think this is only for the PCE working group but should be applicable to the entire rtg area. /Loa On 2014-09-18 10:53, Fatai Zhang wrote: > Hi, > > Sorry, I should say (2b) and (4), :-) > > > > > Best Regards > > Fatai > > > -----Original Message----- > From: Fatai Zhang > Sent: Thursday, September 18, 2014 4:32 PM > To: 'adrian@olddog.co.uk'; pce@ietf.org > Cc: pce-chairs@tools.ietf.org > Subject: RE: [Pce] Preaching about code points in drafts > > Hi Adrian, > > I think the steps you proposed really make sense. > > I have one comment for clarification on step (2a) and (4), did you mean that it only needs to use "TBD" rather than the suggested values? > > In addtion, for the new drafts (or non-existing drafts with clash), can I re-order your steps as follows? :-) > > 1. Do not adopt any I-D as a working group draft if it specifies code points. > > 2. In the future, when implementations of an I-D become advanced enough to be close shipping or starting interop testing, use RFC 7120 to get code points allocated. > > > > > Best Regards > > Fatai > > > -----Original Message----- > From: Pce [mailto:pce-bounces@ietf.org] On Behalf Of Adrian Farrel > Sent: Thursday, September 18, 2014 10:43 AM > To: pce@ietf.org > Cc: pce-chairs@tools.ietf.org > Subject: [Pce] Preaching about code points in drafts > > PCE working group, > > draft-ietf-pce-rfc7150bis is fixing a clash between an IANA allocation for RFC > 7150 and an unallocated code point documented in a working group Internet-Draft > that had been picked up and used by multiple implementations. > > Another clash has just been pointed out to me between RFC 7150 and > draft-ietf-pce-gmpls-pcep-extensions. > > The specifying of unallocated values in PCE I-Ds has got to stop before > significant clashes happen in the field. Cease! Desist! It is not necessary, and > there is a simple solution to get code points if you need them. > > Steps to be followed: > > 1. Identify all I-Ds that state or recommend values for code points (see below). > > 2. Decide whether the values shown are needed to support existing > implementations. > 2a. If so, make an immediate request to the WG chairs for early allocation of > the code points using the procedures of RFC 7120. > 2b. If not, make an immediate revision of the I-D removing the specific code > point values. > > 3. In the future, when implementations of an I-D become advanced enough to be > close shipping or starting interop testing, use RFC 7120 to get code points > allocated. > > 4. Do not adopt any I-D as a working group draft if it specifies code points. > > Current drafts > > draft-ietf-pce-pce-initiated-lsp specifies unallocated values > draft-ietf-pce-pcep-stateful-pce-gmpls suggests values > draft-ietf-pce-remote-initiated-gmpls-lsp specifies an unallocated value > draft-ietf-pce-stateful-pce suggests multiple unallocated values > draft-ietf-pce-stateful-sync-optimizations specifies and suggests multiple > unallocated values > > Recently-expired drafts > > draft-ietf-pce-gmpls-pcep-extensions specifies multiple unallocated values > draft-ietf-pce-inter-layer-ext recommends multiple unallocated values > > > 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 > -- Loa Andersson email: loa@mail01.huawei.com Senior MPLS Expert loa@pi.nu Huawei Technologies (consultant) phone: +46 739 81 21 64 From nobody Thu Sep 18 04:13:50 2014 Return-Path: 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 D8E031A876C for ; Thu, 18 Sep 2014 04:13:45 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.553 X-Spam-Level: X-Spam-Status: No, score=-3.553 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-1.652, 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 Ug_BsWwVQBF4 for ; Thu, 18 Sep 2014 04:13:41 -0700 (PDT) Received: from smtpjc.telefonica.com (smtpjc.telefonica.com [81.47.204.76]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8BEEE1A8713 for ; Thu, 18 Sep 2014 04:13:40 -0700 (PDT) Received: from smtpjc.telefonica.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 7D08C2D020C; Thu, 18 Sep 2014 13:13:37 +0200 (CEST) Received: from ESTGVMSP104.EUROPE.telefonica.corp (unknown [10.92.4.9]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtpjc.telefonica.com (Postfix) with ESMTPS id 6C3672D01EE; Thu, 18 Sep 2014 13:13:37 +0200 (CEST) Received: from emea01-am1-obe.outbound.protection.outlook.com (10.92.5.139) by tls.telefonica.com (10.93.6.50) with Microsoft SMTP Server (TLS) id 14.3.195.1; Thu, 18 Sep 2014 13:13:28 +0200 Received: from AMSPR06MB104.eurprd06.prod.outlook.com (10.242.90.155) by AMSPR06MB102.eurprd06.prod.outlook.com (10.242.90.147) with Microsoft SMTP Server (TLS) id 15.0.1034.13; Thu, 18 Sep 2014 11:12:26 +0000 Received: from AMSPR06MB104.eurprd06.prod.outlook.com ([169.254.8.131]) by AMSPR06MB104.eurprd06.prod.outlook.com ([169.254.8.131]) with mapi id 15.00.1034.003; Thu, 18 Sep 2014 11:12:26 +0000 From: OSCAR GONZALEZ DE DIOS To: Loa Andersson , Fatai Zhang , "adrian@olddog.co.uk" , "pce@ietf.org" Thread-Topic: [Pce] Preaching about code points in drafts Thread-Index: Ac/S6fLxSQSIQaOISi+Ey3mIlZ9+LAALzfkgAAEx46AABKU/AAAEakGA Date: Thu, 18 Sep 2014 11:12:26 +0000 Message-ID: References: <033001cfd2ea$507eef30$f17ccd90$@olddog.co.uk> <541ABC98.5050200@pi.nu> In-Reply-To: <541ABC98.5050200@pi.nu> Accept-Language: es-ES, en-US Content-Language: es-ES X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.3.9.131030 x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [195.235.92.26] x-microsoft-antispam: BCL:0;PCL:0;RULEID:;SRVR:AMSPR06MB102; x-forefront-prvs: 033857D0BD x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(164054003)(24454002)(189002)(199003)(252514010)(53754006)(377424004)(377454003)(479174003)(51704005)(13464003)(86362001)(79102003)(83506001)(92726001)(83322001)(92566001)(19580405001)(74502003)(31966008)(105586002)(36756003)(81342003)(85852003)(15975445006)(74662003)(83072002)(19580395003)(46102003)(81542003)(77982003)(2201001)(80022003)(85306004)(87936001)(77096002)(90102001)(99396002)(54356999)(50986999)(2656002)(76176999)(2501002)(64706001)(97736003)(21056001)(66066001)(76482002)(107046002)(95666004)(106356001)(4396001)(20776003)(101416001); DIR:OUT; SFP:1102; SCL:1; SRVR:AMSPR06MB102; H:AMSPR06MB104.eurprd06.prod.outlook.com; FPR:; MLV:sfv; PTR:InfoNoRecords; MX:1; A:1; LANG:en; Content-Type: text/plain; charset="iso-8859-1" Content-ID: <9CB7697704568442ABD441079A7027C4@eurprd06.prod.outlook.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: telefonica.com X-TM-AS-MML: No Archived-At: http://mailarchive.ietf.org/arch/msg/pce/yUSNLFiaO6IV-6C4JHAycVbkeiA Cc: "pce-chairs@tools.ietf.org" Subject: Re: [Pce] Preaching about code points in drafts X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Sep 2014 11:13:46 -0000 Hi all, I fully agree with the procedure suggested by Adrian. @Fatai. I guess all drafts (stable or not), except those that have an early allocation, will need to have a TBD value. A suggested value is usually (mis)interpreted as =B3this is the specified value, though not official yet=B2 Best Regards, =D3scar El 18/09/14 13:06, "Loa Andersson" escribi=F3: >Fatai, > >I agree with you - I also don't think this is only for the PCE >working group but should be applicable to the entire rtg area. > >/Loa > >On 2014-09-18 10:53, Fatai Zhang wrote: >> Hi, >> >> Sorry, I should say (2b) and (4), :-) >> >> >> >> >> Best Regards >> >> Fatai >> >> >> -----Original Message----- >> From: Fatai Zhang >> Sent: Thursday, September 18, 2014 4:32 PM >> To: 'adrian@olddog.co.uk'; pce@ietf.org >> Cc: pce-chairs@tools.ietf.org >> Subject: RE: [Pce] Preaching about code points in drafts >> >> Hi Adrian, >> >> I think the steps you proposed really make sense. >> >> I have one comment for clarification on step (2a) and (4), did you mean >>that it only needs to use "TBD" rather than the suggested values? >> >> In addtion, for the new drafts (or non-existing drafts with clash), can >>I re-order your steps as follows? :-) >> >> 1. Do not adopt any I-D as a working group draft if it specifies code >>points. >> >> 2. In the future, when implementations of an I-D become advanced enough >>to be close shipping or starting interop testing, use RFC 7120 to get >>code points allocated. >> >> >> >> >> Best Regards >> >> Fatai >> >> >> -----Original Message----- >> From: Pce [mailto:pce-bounces@ietf.org] On Behalf Of Adrian Farrel >> Sent: Thursday, September 18, 2014 10:43 AM >> To: pce@ietf.org >> Cc: pce-chairs@tools.ietf.org >> Subject: [Pce] Preaching about code points in drafts >> >> PCE working group, >> >> draft-ietf-pce-rfc7150bis is fixing a clash between an IANA allocation >>for RFC >> 7150 and an unallocated code point documented in a working group >>Internet-Draft >> that had been picked up and used by multiple implementations. >> >> Another clash has just been pointed out to me between RFC 7150 and >> draft-ietf-pce-gmpls-pcep-extensions. >> >> The specifying of unallocated values in PCE I-Ds has got to stop before >> significant clashes happen in the field. Cease! Desist! It is not >>necessary, and >> there is a simple solution to get code points if you need them. >> >> Steps to be followed: >> >> 1. Identify all I-Ds that state or recommend values for code points >>(see below). >> >> 2. Decide whether the values shown are needed to support existing >> implementations. >> 2a. If so, make an immediate request to the WG chairs for early >>allocation of >> the code points using the procedures of RFC 7120. >> 2b. If not, make an immediate revision of the I-D removing the specific >>code >> point values. >> >> 3. In the future, when implementations of an I-D become advanced enough >>to be >> close shipping or starting interop testing, use RFC 7120 to get code >>points >> allocated. >> >> 4. Do not adopt any I-D as a working group draft if it specifies code >>points. >> >> Current drafts >> >> draft-ietf-pce-pce-initiated-lsp specifies unallocated values >> draft-ietf-pce-pcep-stateful-pce-gmpls suggests values >> draft-ietf-pce-remote-initiated-gmpls-lsp specifies an unallocated value >> draft-ietf-pce-stateful-pce suggests multiple unallocated values >> draft-ietf-pce-stateful-sync-optimizations specifies and suggests >>multiple >> unallocated values >> >> Recently-expired drafts >> >> draft-ietf-pce-gmpls-pcep-extensions specifies multiple unallocated >>values >> draft-ietf-pce-inter-layer-ext recommends multiple unallocated values >> >> >> 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 >> > >-- > > >Loa Andersson email: loa@mail01.huawei.com >Senior MPLS Expert loa@pi.nu >Huawei Technologies (consultant) phone: +46 739 81 21 64 > >_______________________________________________ >Pce mailing list >Pce@ietf.org >https://www.ietf.org/mailman/listinfo/pce ________________________________ Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, pu= ede contener informaci=F3n privilegiada o confidencial y es para uso exclus= ivo de la persona o entidad de destino. Si no es usted. el destinatario ind= icado, queda notificado de que la lectura, utilizaci=F3n, divulgaci=F3n y/o= copia sin autorizaci=F3n puede estar prohibida en virtud de la legislaci= =F3n vigente. Si ha recibido este mensaje por error, le rogamos que nos lo = comunique inmediatamente por esta misma v=EDa y proceda a su destrucci=F3n. The information contained in this transmission is privileged and confidenti= al information intended only for the use of the individual or entity named = above. If the reader of this message is not the intended recipient, you are= hereby notified that any dissemination, distribution or copying of this co= mmunication is strictly prohibited. If you have received this transmission = in error, do not read it. Please immediately reply to the sender that you h= ave received this communication in error and then delete it. Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat=E1rio= , pode conter informa=E7=E3o privilegiada ou confidencial e =E9 para uso ex= clusivo da pessoa ou entidade de destino. Se n=E3o =E9 vossa senhoria o des= tinat=E1rio indicado, fica notificado de que a leitura, utiliza=E7=E3o, div= ulga=E7=E3o e/ou c=F3pia sem autoriza=E7=E3o pode estar proibida em virtude= da legisla=E7=E3o vigente. Se recebeu esta mensagem por erro, rogamos-lhe = que nos o comunique imediatamente por esta mesma via e proceda a sua destru= i=E7=E3o From nobody Thu Sep 18 04:26:47 2014 Return-Path: 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 9A8FA1A014D for ; Thu, 18 Sep 2014 04:26:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.552 X-Spam-Level: X-Spam-Status: No, score=-3.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.652] 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 X2s0XY1C1_-3 for ; Thu, 18 Sep 2014 04:26:42 -0700 (PDT) Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4E7F31A017C for ; Thu, 18 Sep 2014 04:26:42 -0700 (PDT) Received: from [192.168.0.106] (81-229-83-119-no65.business.telia.com [81.229.83.119]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id 7B37C180131A; Thu, 18 Sep 2014 13:26:40 +0200 (CEST) Message-ID: <541AC171.80500@pi.nu> Date: Thu, 18 Sep 2014 13:26:41 +0200 From: Loa Andersson User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: OSCAR GONZALEZ DE DIOS , Fatai Zhang , "adrian@olddog.co.uk" , "pce@ietf.org" References: <033001cfd2ea$507eef30$f17ccd90$@olddog.co.uk> <541ABC98.5050200@pi.nu> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Archived-At: http://mailarchive.ietf.org/arch/msg/pce/Zb4mznKsP7tncCleiDzNWFquIiM Cc: "pce-chairs@tools.ietf.org" Subject: Re: [Pce] Preaching about code points in drafts X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Sep 2014 11:26:44 -0000 Oscar, yes - true, but there are also FCFS allocations, such a code point allocation can be made for any document (also an individual draft). /Loa On 2014-09-18 13:12, OSCAR GONZALEZ DE DIOS wrote: > Hi all, > > I fully agree with the procedure suggested by Adrian. > > @Fatai. I guess all drafts (stable or not), except those that have an > early allocation, will need to have a TBD value. A suggested value is > usually (mis)interpreted as ³this is the specified value, though not > official yet² > > Best Regards, > > Óscar > > El 18/09/14 13:06, "Loa Andersson" escribió: > >> Fatai, >> >> I agree with you - I also don't think this is only for the PCE >> working group but should be applicable to the entire rtg area. >> >> /Loa >> >> On 2014-09-18 10:53, Fatai Zhang wrote: >>> Hi, >>> >>> Sorry, I should say (2b) and (4), :-) >>> >>> >>> >>> >>> Best Regards >>> >>> Fatai >>> >>> >>> -----Original Message----- >>> From: Fatai Zhang >>> Sent: Thursday, September 18, 2014 4:32 PM >>> To: 'adrian@olddog.co.uk'; pce@ietf.org >>> Cc: pce-chairs@tools.ietf.org >>> Subject: RE: [Pce] Preaching about code points in drafts >>> >>> Hi Adrian, >>> >>> I think the steps you proposed really make sense. >>> >>> I have one comment for clarification on step (2a) and (4), did you mean >>> that it only needs to use "TBD" rather than the suggested values? >>> >>> In addtion, for the new drafts (or non-existing drafts with clash), can >>> I re-order your steps as follows? :-) >>> >>> 1. Do not adopt any I-D as a working group draft if it specifies code >>> points. >>> >>> 2. In the future, when implementations of an I-D become advanced enough >>> to be close shipping or starting interop testing, use RFC 7120 to get >>> code points allocated. >>> >>> >>> >>> >>> Best Regards >>> >>> Fatai >>> >>> >>> -----Original Message----- >>> From: Pce [mailto:pce-bounces@ietf.org] On Behalf Of Adrian Farrel >>> Sent: Thursday, September 18, 2014 10:43 AM >>> To: pce@ietf.org >>> Cc: pce-chairs@tools.ietf.org >>> Subject: [Pce] Preaching about code points in drafts >>> >>> PCE working group, >>> >>> draft-ietf-pce-rfc7150bis is fixing a clash between an IANA allocation >>> for RFC >>> 7150 and an unallocated code point documented in a working group >>> Internet-Draft >>> that had been picked up and used by multiple implementations. >>> >>> Another clash has just been pointed out to me between RFC 7150 and >>> draft-ietf-pce-gmpls-pcep-extensions. >>> >>> The specifying of unallocated values in PCE I-Ds has got to stop before >>> significant clashes happen in the field. Cease! Desist! It is not >>> necessary, and >>> there is a simple solution to get code points if you need them. >>> >>> Steps to be followed: >>> >>> 1. Identify all I-Ds that state or recommend values for code points >>> (see below). >>> >>> 2. Decide whether the values shown are needed to support existing >>> implementations. >>> 2a. If so, make an immediate request to the WG chairs for early >>> allocation of >>> the code points using the procedures of RFC 7120. >>> 2b. If not, make an immediate revision of the I-D removing the specific >>> code >>> point values. >>> >>> 3. In the future, when implementations of an I-D become advanced enough >>> to be >>> close shipping or starting interop testing, use RFC 7120 to get code >>> points >>> allocated. >>> >>> 4. Do not adopt any I-D as a working group draft if it specifies code >>> points. >>> >>> Current drafts >>> >>> draft-ietf-pce-pce-initiated-lsp specifies unallocated values >>> draft-ietf-pce-pcep-stateful-pce-gmpls suggests values >>> draft-ietf-pce-remote-initiated-gmpls-lsp specifies an unallocated value >>> draft-ietf-pce-stateful-pce suggests multiple unallocated values >>> draft-ietf-pce-stateful-sync-optimizations specifies and suggests >>> multiple >>> unallocated values >>> >>> Recently-expired drafts >>> >>> draft-ietf-pce-gmpls-pcep-extensions specifies multiple unallocated >>> values >>> draft-ietf-pce-inter-layer-ext recommends multiple unallocated values >>> >>> >>> 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 >>> >> >> -- >> >> >> Loa Andersson email: loa@mail01.huawei.com >> Senior MPLS Expert loa@pi.nu >> Huawei Technologies (consultant) phone: +46 739 81 21 64 >> >> _______________________________________________ >> Pce mailing list >> Pce@ietf.org >> https://www.ietf.org/mailman/listinfo/pce > > > ________________________________ > > Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción. > > The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it. > > Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição > -- Loa Andersson email: loa@mail01.huawei.com Senior MPLS Expert loa@pi.nu Huawei Technologies (consultant) phone: +46 739 81 21 64 From nobody Thu Sep 18 05:52:27 2014 Return-Path: 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 A7FAD1A02D5; Thu, 18 Sep 2014 05:52:21 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.852 X-Spam-Level: X-Spam-Status: No, score=-0.852 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-1.652, 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 kQXynWo3ujGf; Thu, 18 Sep 2014 05:52:19 -0700 (PDT) Received: from smtptc.telefonica.com (smtptc.telefonica.com [195.76.34.108]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AFF561A878D; Thu, 18 Sep 2014 05:52:12 -0700 (PDT) Received: from smtptc.telefonica.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id B27BE3A00FF; Thu, 18 Sep 2014 14:52:10 +0200 (CEST) Received: from ESTGVMSP113.EUROPE.telefonica.corp (unknown [10.92.4.9]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtptc.telefonica.com (Postfix) with ESMTPS id 9C6DF3A00C9; Thu, 18 Sep 2014 14:52:10 +0200 (CEST) Received: from emea01-am1-obe.outbound.protection.outlook.com (10.92.5.139) by tls.telefonica.com (10.92.6.55) with Microsoft SMTP Server (TLS) id 14.3.195.1; Thu, 18 Sep 2014 14:52:10 +0200 Received: from AMSPR06MB104.eurprd06.prod.outlook.com (10.242.90.155) by AMSPR06MB104.eurprd06.prod.outlook.com (10.242.90.155) with Microsoft SMTP Server (TLS) id 15.0.1034.13; Thu, 18 Sep 2014 12:52:07 +0000 Received: from AMSPR06MB104.eurprd06.prod.outlook.com ([169.254.8.131]) by AMSPR06MB104.eurprd06.prod.outlook.com ([169.254.8.131]) with mapi id 15.00.1034.003; Thu, 18 Sep 2014 12:52:07 +0000 From: OSCAR GONZALEZ DE DIOS To: "pce@ietf.org" , "pce-chairs@ietf.org" Thread-Topic: Ask for early allocation of code-points of draft-ietf-pce-gmpls-pcep-extensions Thread-Index: AQHP0z9aZo3N6pvB8kObsAPNomK3jg== Date: Thu, 18 Sep 2014 12:52:07 +0000 Message-ID: Accept-Language: es-ES, en-US Content-Language: es-ES X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.3.9.131030 x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [195.235.92.26] x-microsoft-antispam: BCL:0;PCL:0;RULEID:;SRVR:AMSPR06MB104; x-forefront-prvs: 033857D0BD x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(199003)(189002)(77096002)(81542003)(106116001)(80022003)(46102003)(77982003)(79102003)(74502003)(21056001)(64706001)(66066001)(74662003)(81342003)(20776003)(97736003)(230783001)(2501002)(76482002)(85306004)(229853001)(36756003)(105586002)(106356001)(107046002)(90102001)(95666004)(4396001)(107886001)(83506001)(50986999)(83072002)(85852003)(54356999)(92566001)(86362001)(92726001)(16236675004)(31966008)(83322001)(2656002)(87936001)(99396002)(101416001); DIR:OUT; SFP:1102; SCL:1; SRVR:AMSPR06MB104; H:AMSPR06MB104.eurprd06.prod.outlook.com; FPR:; MLV:sfv; PTR:InfoNoRecords; A:1; MX:1; LANG:en; Content-Type: multipart/alternative; boundary="_000_D040A2166374Foscargonzalezdediostelefonicacom_" MIME-Version: 1.0 X-OriginatorOrg: telefonica.com X-TM-AS-MML: No Archived-At: http://mailarchive.ietf.org/arch/msg/pce/5A0sqLbq9uQdSLEfgUEqrzHl6Eg Subject: [Pce] Ask for early allocation of code-points of draft-ietf-pce-gmpls-pcep-extensions X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Sep 2014 12:52:21 -0000 --_000_D040A2166374Foscargonzalezdediostelefonicacom_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Dear PCE WG chairs, PCErs, The document draft-ietf-pce-gmpls-pcep-extensions has been stable for a whi= le and it is near LC completion (the document started in 2010). There are e= arly implementations of the draft. In my opinion, it is of high value to ha= ve early allocated values to support such implementations. Authors of draft-ietf-pce-gmpls-pcep-extensions would like to request IAN= A the early allocation of the code-points included in draft-ietf-pce-gmpls-= pcep-extensions. We would like to ask PCErs if they see necessary the early allocation of co= de points in draft-ietf-pce-gmpls-pcep-extensions. Best Regards, =D3scar ________________________________ Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, pu= ede contener informaci=F3n privilegiada o confidencial y es para uso exclus= ivo de la persona o entidad de destino. Si no es usted. el destinatario ind= icado, queda notificado de que la lectura, utilizaci=F3n, divulgaci=F3n y/o= copia sin autorizaci=F3n puede estar prohibida en virtud de la legislaci= =F3n vigente. Si ha recibido este mensaje por error, le rogamos que nos lo = comunique inmediatamente por esta misma v=EDa y proceda a su destrucci=F3n. The information contained in this transmission is privileged and confidenti= al information intended only for the use of the individual or entity named = above. If the reader of this message is not the intended recipient, you are= hereby notified that any dissemination, distribution or copying of this co= mmunication is strictly prohibited. If you have received this transmission = in error, do not read it. Please immediately reply to the sender that you h= ave received this communication in error and then delete it. Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat=E1rio= , pode conter informa=E7=E3o privilegiada ou confidencial e =E9 para uso ex= clusivo da pessoa ou entidade de destino. Se n=E3o =E9 vossa senhoria o des= tinat=E1rio indicado, fica notificado de que a leitura, utiliza=E7=E3o, div= ulga=E7=E3o e/ou c=F3pia sem autoriza=E7=E3o pode estar proibida em virtude= da legisla=E7=E3o vigente. Se recebeu esta mensagem por erro, rogamos-lhe = que nos o comunique imediatamente por esta mesma via e proceda a sua destru= i=E7=E3o --_000_D040A2166374Foscargonzalezdediostelefonicacom_ Content-Type: text/html; charset="iso-8859-1" Content-ID: Content-Transfer-Encoding: quoted-printable
Dear PCE WG chairs, PCErs,

The do= cument draft-ietf-pce-gmpls-pcep-extensions has been stable for a whil= e and it is near LC completion (the document started in 2010). There are ea= rly implementations of the draft. In my opinion, it is of high value to have early allocated values to support such impleme= ntations.  

&nbs= p;Authors of  draft-ietf-pce-gmpls-pcep-extensions would like to reque= st IANA the early allocation of the code-points included in draft-ietf= -pce-gmpls-pcep-extensions. 

We&nbs= p;would like to ask PCErs if they see necessary the early allocation of cod= e points in draft-ietf-pce-gmpls-pcep-extensions. 

Best R= egards,

=D3sca= r




Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, pu= ede contener informaci=F3n privilegiada o confidencial y es para uso exclus= ivo de la persona o entidad de destino. Si no es usted. el destinatario ind= icado, queda notificado de que la lectura, utilizaci=F3n, divulgaci=F3n y/o copia sin autorizaci=F3n puede e= star prohibida en virtud de la legislaci=F3n vigente. Si ha recibido este m= ensaje por error, le rogamos que nos lo comunique inmediatamente por esta m= isma v=EDa y proceda a su destrucci=F3n.

The information contained in this transmission is privileged and confidenti= al information intended only for the use of the individual or entity named = above. If the reader of this message is not the intended recipient, you are= hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If y= ou have received this transmission in error, do not read it. Please immedia= tely reply to the sender that you have received this communication in error= and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat=E1rio= , pode conter informa=E7=E3o privilegiada ou confidencial e =E9 para uso ex= clusivo da pessoa ou entidade de destino. Se n=E3o =E9 vossa senhoria o des= tinat=E1rio indicado, fica notificado de que a leitura, utiliza=E7=E3o, divulga=E7=E3o e/ou c=F3pia sem autoriza=E7=E3o p= ode estar proibida em virtude da legisla=E7=E3o vigente. Se recebeu esta me= nsagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mes= ma via e proceda a sua destrui=E7=E3o
 --_000_D040A2166374Foscargonzalezdediostelefonicacom_-- From nobody Thu Sep 18 10:26:25 2014 Return-Path: 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 A440F1A0437 for ; Thu, 18 Sep 2014 10:26:21 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.9 X-Spam-Level: X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, USER_IN_WHITELIST=-100] 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 wVgW1eoX-A8K for ; Thu, 18 Sep 2014 10:26:19 -0700 (PDT) Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 36AE61A015F for ; Thu, 18 Sep 2014 10:26:18 -0700 (PDT) Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id s8IHQ7RS015342; Thu, 18 Sep 2014 18:26:07 +0100 Received: from 950129200 (176-227-128-84.ip.skylogicnet.com [176.227.128.84]) (authenticated bits=0) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id s8IHPsmU015295 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 18 Sep 2014 18:26:00 +0100 From: "Adrian Farrel" To: "'Loa Andersson'" , "'OSCAR GONZALEZ DE DIOS'" , "'Fatai Zhang'" , References: <033001cfd2ea$507eef30$f17ccd90$@olddog.co.uk> <541ABC98.5050200@pi.nu> <541AC171.80500@pi.nu> In-Reply-To: <541AC171.80500@pi.nu> Date: Thu, 18 Sep 2014 18:25:52 +0100 Message-ID: <050701cfd365$9fa10000$dee30000$@olddog.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQGCkho/Jx0In6Sw25cIwLwJ6KwgdgH8Xq0lArLJQv4BsZ1lmwHtbDg3nF801cA= Content-Language: en-gb X-TM-AS-MML: disable X-TM-AS-Product-Ver: IMSS-7.1.0.1576-7.5.0.1018-20962.001 X-TM-AS-Result: No--35.492-10.0-31-10 X-imss-scan-details: No--35.492-10.0-31-10 X-TMASE-MatchedRID: IeZYkn8zfFov2k3M27J31pU7Bltw5qVL7h2RrsKOiu2CsBeCv8CM/REX WgyXQw/xTWLw2jvbfpzmKLFYcKpv/Tj4RKrox6Ifug9L9GJz8MsZskwWqoib3Mlgi/vLS272Arf whXClRwnUXduftfjvRzeT288mssTU3GEIy0YVWjZpR7+L0B6mEyOSuAnftGqPYz65TQfoDKtvHJ RPzHpwI8t/Qoa91KS/CmjHXhV21s10tMeOizCSGpmug812qIbz0HjeANoeuJ3FpA1uJFd1mkRhT o40MtNYbNZroh3IjpedDe9G+rkqX5PTvqrK6m5BlGudLLtRO1sY/HbtHY2se56fSoF3Lt+MFtnj ZonmoTfI20bQKHH9zr+vO5/XtJEIcKqcXQuOZ6YE+55ERuBQoRLXa2P1m93zydovWuL+KVfbNQh 85GhqIhFbcWj6Erew2zpkBt6vsmzGkynrj1kccnvJQVeTfo7Wve4yDRKn3VXVvyi4nKN3tsXALw /qI5x0TvTXNfSXt6WWHKNDzx+BbFIFXwd39Ncdo31QqQwlT773/XZlf1aRGa2iEsLkgv/TLELEz x+BGHwspZM17LnhEyrJrjKVBKod9Shphytz4/dG5RofwyZtgLThbcx5ma3uj6UdUkdgVBGoWL4k nYFZ2gYNQQy6pC1qbmJbTJ/G9NghoN56wzLfGkj2sPWKvtn0Y9JlLwL1dg3KY//WmIj/oYu3tdA XbWvtcrX2yaJcE9k6W25e1Bs1RC5Am3YGl5jJxDtI40oHM24HKWe50gvaCWDh/NS68cfPt75xoG v0bmcdzHaN81uJhbLTBrnYJroj+v4e0jKvZcGeAiCmPx4NwGNn8XPiALIbtrNGq+WQEvR88Plw9 Yn01wtuKBGekqUpPjKoPgsq7cA= Archived-At: http://mailarchive.ietf.org/arch/msg/pce/aKYlgQvhCCoG9XqQFLf0o0G51yQ Cc: pce-chairs@tools.ietf.org Subject: Re: [Pce] Preaching about code points in drafts X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: adrian@olddog.co.uk List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Sep 2014 17:26:21 -0000 Right to all of you. FCFS is already allocated, so that is OK. TBD is what we want otherwise. That is no "recommendation" and no "specification". I would say, however, that sometimes it *is* appropriate to recommend = values for IANA when there is a special reason for a particular value, but that = reason is not strong enough to do early allocation. A > -----Original Message----- > From: Loa Andersson [mailto:loa@pi.nu] > Sent: 18 September 2014 12:27 > To: OSCAR GONZALEZ DE DIOS; Fatai Zhang; adrian@olddog.co.uk; = pce@ietf.org > Cc: pce-chairs@tools.ietf.org > Subject: Re: [Pce] Preaching about code points in drafts >=20 > Oscar, >=20 > yes - true, but there are also FCFS allocations, such a code point > allocation can be made for any document (also an individual draft). >=20 > /Loa >=20 > On 2014-09-18 13:12, OSCAR GONZALEZ DE DIOS wrote: > > Hi all, > > > > I fully agree with the procedure suggested by Adrian. > > > > @Fatai. I guess all drafts (stable or not), except those that = have an > > early allocation, will need to have a TBD value. A suggested value = is > > usually (mis)interpreted as =B3this is the specified value, though = not > > official yet=B2 > > > > Best Regards, > > > > =D3scar > > > > El 18/09/14 13:06, "Loa Andersson" escribi=F3: > > > >> Fatai, > >> > >> I agree with you - I also don't think this is only for the PCE > >> working group but should be applicable to the entire rtg area. > >> > >> /Loa > >> > >> On 2014-09-18 10:53, Fatai Zhang wrote: > >>> Hi, > >>> > >>> Sorry, I should say (2b) and (4), :-) > >>> > >>> > >>> > >>> > >>> Best Regards > >>> > >>> Fatai > >>> > >>> > >>> -----Original Message----- > >>> From: Fatai Zhang > >>> Sent: Thursday, September 18, 2014 4:32 PM > >>> To: 'adrian@olddog.co.uk'; pce@ietf.org > >>> Cc: pce-chairs@tools.ietf.org > >>> Subject: RE: [Pce] Preaching about code points in drafts > >>> > >>> Hi Adrian, > >>> > >>> I think the steps you proposed really make sense. > >>> > >>> I have one comment for clarification on step (2a) and (4), did you = mean > >>> that it only needs to use "TBD" rather than the suggested values? > >>> > >>> In addtion, for the new drafts (or non-existing drafts with = clash), can > >>> I re-order your steps as follows? :-) > >>> > >>> 1. Do not adopt any I-D as a working group draft if it specifies = code > >>> points. > >>> > >>> 2. In the future, when implementations of an I-D become advanced = enough > >>> to be close shipping or starting interop testing, use RFC 7120 to = get > >>> code points allocated. > >>> > >>> > >>> > >>> > >>> Best Regards > >>> > >>> Fatai > >>> > >>> > >>> -----Original Message----- > >>> From: Pce [mailto:pce-bounces@ietf.org] On Behalf Of Adrian Farrel > >>> Sent: Thursday, September 18, 2014 10:43 AM > >>> To: pce@ietf.org > >>> Cc: pce-chairs@tools.ietf.org > >>> Subject: [Pce] Preaching about code points in drafts > >>> > >>> PCE working group, > >>> > >>> draft-ietf-pce-rfc7150bis is fixing a clash between an IANA = allocation > >>> for RFC > >>> 7150 and an unallocated code point documented in a working group > >>> Internet-Draft > >>> that had been picked up and used by multiple implementations. > >>> > >>> Another clash has just been pointed out to me between RFC 7150 and > >>> draft-ietf-pce-gmpls-pcep-extensions. > >>> > >>> The specifying of unallocated values in PCE I-Ds has got to stop = before > >>> significant clashes happen in the field. Cease! Desist! It is not > >>> necessary, and > >>> there is a simple solution to get code points if you need them. > >>> > >>> Steps to be followed: > >>> > >>> 1. Identify all I-Ds that state or recommend values for code = points > >>> (see below). > >>> > >>> 2. Decide whether the values shown are needed to support existing > >>> implementations. > >>> 2a. If so, make an immediate request to the WG chairs for early > >>> allocation of > >>> the code points using the procedures of RFC 7120. > >>> 2b. If not, make an immediate revision of the I-D removing the = specific > >>> code > >>> point values. > >>> > >>> 3. In the future, when implementations of an I-D become advanced = enough > >>> to be > >>> close shipping or starting interop testing, use RFC 7120 to get = code > >>> points > >>> allocated. > >>> > >>> 4. Do not adopt any I-D as a working group draft if it specifies = code > >>> points. > >>> > >>> Current drafts > >>> > >>> draft-ietf-pce-pce-initiated-lsp specifies unallocated values > >>> draft-ietf-pce-pcep-stateful-pce-gmpls suggests values > >>> draft-ietf-pce-remote-initiated-gmpls-lsp specifies an unallocated = value > >>> draft-ietf-pce-stateful-pce suggests multiple unallocated values > >>> draft-ietf-pce-stateful-sync-optimizations specifies and suggests > >>> multiple > >>> unallocated values > >>> > >>> Recently-expired drafts > >>> > >>> draft-ietf-pce-gmpls-pcep-extensions specifies multiple = unallocated > >>> values > >>> draft-ietf-pce-inter-layer-ext recommends multiple unallocated = values > >>> > >>> > >>> 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 > >>> > >> > >> -- > >> > >> > >> Loa Andersson email: loa@mail01.huawei.com > >> Senior MPLS Expert loa@pi.nu > >> Huawei Technologies (consultant) phone: +46 739 81 21 64 > >> > >> _______________________________________________ > >> Pce mailing list > >> Pce@ietf.org > >> https://www.ietf.org/mailman/listinfo/pce > > > > > > ________________________________ > > > > Este mensaje y sus adjuntos se dirigen exclusivamente a su = destinatario, puede > contener informaci=F3n privilegiada o confidencial y es para uso = exclusivo de la > persona o entidad de destino. Si no es usted. el destinatario = indicado, queda > notificado de que la lectura, utilizaci=F3n, divulgaci=F3n y/o copia = sin autorizaci=F3n > puede estar prohibida en virtud de la legislaci=F3n vigente. Si ha = recibido este > mensaje por error, le rogamos que nos lo comunique inmediatamente por = esta > misma v=EDa y proceda a su destrucci=F3n. > > > > The information contained in this transmission is privileged and confidential > information intended only for the use of the individual or entity = named above. If > the reader of this message is not the intended recipient, you are = hereby notified > that any dissemination, distribution or copying of this communication = is strictly > prohibited. If you have received this transmission in error, do not = read it. Please > immediately reply to the sender that you have received this = communication in > error and then delete it. > > > > Esta mensagem e seus anexos se dirigem exclusivamente ao seu = destinat=E1rio, > pode conter informa=E7=E3o privilegiada ou confidencial e =E9 para uso = exclusivo da > pessoa ou entidade de destino. Se n=E3o =E9 vossa senhoria o = destinat=E1rio indicado, > fica notificado de que a leitura, utiliza=E7=E3o, divulga=E7=E3o e/ou = c=F3pia sem autoriza=E7=E3o > pode estar proibida em virtude da legisla=E7=E3o vigente. Se recebeu = esta mensagem > por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma = via > e proceda a sua destrui=E7=E3o > > >=20 > -- >=20 >=20 > Loa Andersson email: loa@mail01.huawei.com > Senior MPLS Expert loa@pi.nu > Huawei Technologies (consultant) phone: +46 739 81 21 64 From nobody Thu Sep 18 13:50:50 2014 Return-Path: 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 D50C01A8942 for ; Thu, 18 Sep 2014 13:50:40 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -16.152 X-Spam-Level: X-Spam-Status: No, score=-16.152 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.652, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 mBPQJ2-gR_rx for ; Thu, 18 Sep 2014 13:50:37 -0700 (PDT) Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E44841A8935 for ; Thu, 18 Sep 2014 13:50:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4722; q=dns/txt; s=iport; t=1411073437; x=1412283037; h=from:to:subject:date:message-id:references:mime-version; bh=U9IGFaGvYsyt/Ptzuut77OO4hiL3S/7af8HgcqRA8p4=; b=Vh1JbyV7axtKv+6H4hjAFjY2URZoJphK1DLdD1dpYLA7qb3UOFwUjRDE RxW0ZAOiqhfRiAlJ0GeQ7kiy3AicUIJ7Q47LKVGJsaNXz+zVF0R36lcHW nAhXN0+M3mfHB2iEal8H+xua/RR+eg+MpOBKrTD1cvglV1iGkr8dPMGp9 Y=; X-Files: signature.asc : 496 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApMHAM9EG1StJA2D/2dsb2JhbABggw1TVwTJPQEJh02BDBYBcQiEAwEBAQMBAQEBaxALAgEMDQMBAi8nCxsCCAIEEw6IKAgNwj4BEwSPZh6DKIEdBY84ghaCCIFLh2uVSIIbgUNsgUiBAgEBAQ X-IronPort-AV: E=Sophos;i="5.04,549,1406592000"; d="asc'?scan'208,217";a="353288251" Received: from alln-core-1.cisco.com ([173.36.13.131]) by rcdn-iport-9.cisco.com with ESMTP; 18 Sep 2014 20:50:36 +0000 Received: from xhc-aln-x11.cisco.com (xhc-aln-x11.cisco.com [173.36.12.85]) by alln-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s8IKoamK000610 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for ; Thu, 18 Sep 2014 20:50:36 GMT Received: from xmb-rcd-x02.cisco.com ([169.254.4.84]) by xhc-aln-x11.cisco.com ([173.36.12.85]) with mapi id 14.03.0195.001; Thu, 18 Sep 2014 15:50:35 -0500 From: "JP Vasseur (jvasseur)" To: "pce@ietf.org" Thread-Topic: [Pce] Adoption of draft-sivabalan-pce-lsp-setup-type-02.txt as a PCE WG Document Thread-Index: AQHP04IypDeyCETlg0if2BAN7XwQLg== Date: Thu, 18 Sep 2014 20:50:35 +0000 Message-ID: References: <70E9F53F-3A40-4CC6-924B-9BA229FD84AA@cisco.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: x-originating-ip: [10.61.101.16] Content-Type: multipart/signed; boundary="Apple-Mail=_A58BE60E-EEFD-42FE-B66B-863DA24F4AA5"; protocol="application/pgp-signature"; micalg=pgp-sha512 MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/pce/oPKGhGTMaKx23jL5iz7nXtF-jx8 Subject: [Pce] Fwd: Adoption of draft-sivabalan-pce-lsp-setup-type-02.txt as a PCE WG Document X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Sep 2014 20:50:41 -0000 --Apple-Mail=_A58BE60E-EEFD-42FE-B66B-863DA24F4AA5 Content-Type: multipart/alternative; boundary="Apple-Mail=_C998116E-2E22-4A61-ACCD-E734FDA12D7A" --Apple-Mail=_C998116E-2E22-4A61-ACCD-E734FDA12D7A Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Dear WG, There is a clear consensus: authors please resubmit as = draft-ietf-pce-lsp-setup-type-00.txt, with no other change than title, date. Thanks. JP. Begin forwarded message: > From: "JP Vasseur (jvasseur)" > Subject: [Pce] Adoption of draft-sivabalan-pce-lsp-setup-type-02.txt = as a PCE WG Document > Date: September 14, 2014 at 12:06:24 PM GMT+2 > To: "pce@ietf.org" >=20 > Dear WG, >=20 > We had several discussions showing a good consensus adopting = draft-sivabalan-pce-lsp-setup-type-02.txt and this work > has considerably progressed in other WG. >=20 > Are you in favor of adopting draft-sivabalan-pce-lsp-setup-type-02.txt = as a PCE WG document ? >=20 > Thanks. >=20 > JP and Julien. > _______________________________________________ > Pce mailing list > Pce@ietf.org > https://www.ietf.org/mailman/listinfo/pce --Apple-Mail=_C998116E-2E22-4A61-ACCD-E734FDA12D7A Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii Dear = WG,

There is a clear consensus: authors please = resubmit as draft-ietf-pce-lsp-setup-type-00.txt, with = no
other change than title, = date.

Thanks.

JP.
<= div>

Begin forwarded message:

From: "JP Vasseur (jvasseur)" <jvasseur@cisco.com>
Subject: [Pce] Adoption of = draft-sivabalan-pce-lsp-setup-type-02.txt as a PCE WG = Document
Date: = September 14, 2014 = at 12:06:24 PM GMT+2

Dear WG,

We had several discussions showing a good consensus = adopting draft-sivabalan-pce-lsp-setup-type-02.txt and this work
has = considerably progressed in other WG.

Are you in favor of adopting = draft-sivabalan-pce-lsp-setup-type-02.txt as a PCE WG document = ?

Thanks.

JP and = Julien.
_______________________________________________
Pce = mailing list
Pce@ietf.org
https://www.ietf.org/mail= man/listinfo/pce

= --Apple-Mail=_C998116E-2E22-4A61-ACCD-E734FDA12D7A-- --Apple-Mail=_A58BE60E-EEFD-42FE-B66B-863DA24F4AA5 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="signature.asc" Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQEcBAEBCgAGBQJUG0WbAAoJEHBVWzpLl1Mtt3wH/ipg/ng/SwjnxblPhn8rEQoK XGtjdpjOu2qXLwf8dLaWfRzZZopHmY2kIWiyeojJ6H5aA6vMh6mmRCV98A7NNy6X 9kB7MD+dOYKTuTUbReQf4EJJbYczchXHj9pbls2r1iFlHgzjE/yXAQBhUYMFyz7Z UMAXH9CIZoe9hs489BHtcYbdWMbLJJMmB8YdQl83JabOv6NxMV/HJi2/L9PX327l 8PGJ78ri51ZF8X6Ty5JPg0AfxMo4uOxyriMG+k593Eu0Xn3vULMQVAQLiNxqMwwY Yh63NglCHqcEYuQPPyEFxvDUDVioumEmifLXul/ifzWgef8lfKkT5h/ddB4jjUk= =WwF+ -----END PGP SIGNATURE----- --Apple-Mail=_A58BE60E-EEFD-42FE-B66B-863DA24F4AA5-- From nobody Thu Sep 18 13:51:10 2014 Return-Path: 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 0258F1A8932 for ; Thu, 18 Sep 2014 13:51:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -16.152 X-Spam-Level: X-Spam-Status: No, score=-16.152 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.652, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 knzIehs2wstM for ; Thu, 18 Sep 2014 13:51:00 -0700 (PDT) Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 853B21A893F for ; Thu, 18 Sep 2014 13:50:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5597; q=dns/txt; s=iport; t=1411073453; x=1412283053; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=2iC+EojZu7YLAnSe3hcc1p8hADIkYadFo6DmSauITlo=; b=X9MkLnewql+Ffn77m4YZzdIkcNBgjstq2yz2pzQDMNC+wiJtUKHzLvZt wzlfeG0+FRQWH+BeD5DZLzsXAnjFJIMbZqlJW900KMEvRM25ARkFpnIY3 v0aIFvWw7/hlyIXUXe3xPdpUMsgDXZgNyLS3yo/5PON+c0DzVqeT88Go4 0=; X-Files: signature.asc : 496 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApQHAHBFG1StJA2I/2dsb2JhbABggw1TVwTJPQEJh00BgQsWAXEIhAMBAQEDAQEBAWsbAgEIBA0DAQIvJwsdCAIEEw6IKAgNwkEBEwSPZg0LBoMogR0FjziCFoIIgUuHa5VIghuBQ2yBSIECAQEB X-IronPort-AV: E=Sophos;i="5.04,549,1406592000"; d="asc'?scan'208,217";a="356466772" Received: from alln-core-3.cisco.com ([173.36.13.136]) by rcdn-iport-4.cisco.com with ESMTP; 18 Sep 2014 20:50:30 +0000 Received: from xhc-rcd-x11.cisco.com (xhc-rcd-x11.cisco.com [173.37.183.85]) by alln-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id s8IKoUnR019006 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for ; Thu, 18 Sep 2014 20:50:30 GMT Received: from xmb-rcd-x02.cisco.com ([169.254.4.84]) by xhc-rcd-x11.cisco.com ([173.37.183.85]) with mapi id 14.03.0195.001; Thu, 18 Sep 2014 15:50:29 -0500 From: "JP Vasseur (jvasseur)" To: "pce@ietf.org" Thread-Topic: [Pce] Adopting of draft-sivabalan-pce-segment-routing-03.txt as PCE WG Document Thread-Index: AQHP04IuMiXNkzax+UCOtVuaXBmPOw== Date: Thu, 18 Sep 2014 20:50:29 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: x-originating-ip: [10.61.101.16] Content-Type: multipart/signed; boundary="Apple-Mail=_C9379C92-4C79-49C8-AD50-D4344F390A28"; protocol="application/pgp-signature"; micalg=pgp-sha512 MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/pce/wRCrs_y1vqIa7wBRkYeS-cei2OI Subject: Re: [Pce] Adopting of draft-sivabalan-pce-segment-routing-03.txt as PCE WG Document X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Sep 2014 20:51:04 -0000 --Apple-Mail=_C9379C92-4C79-49C8-AD50-D4344F390A28 Content-Type: multipart/alternative; boundary="Apple-Mail=_9FA63404-10F7-428F-8A37-84C7E066D351" --Apple-Mail=_9FA63404-10F7-428F-8A37-84C7E066D351 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Dear WG, There is a clear consensus: authors please resubmit as = draft-ietf-pce-segment-routing-00.txt, with no other change than title, date. Thanks. JP. On Sep 14, 2014, at 3:54 PM, JP Vasseur (jvasseur) = wrote: >=20 >=20 > Begin forwarded message: >=20 >> From: "JP Vasseur (jvasseur)" >> Subject: [Pce] Adopting of draft-sivabalan-pce-segment-routing-03.txt = as PCE WG Document >> Date: September 14, 2014 at 12:06:28 PM GMT+2 >> To: "pce@ietf.org" >>=20 >> Dear WG, >>=20 >> We had several discussions showing a good consensus adopting = draft-sivabalan-pce-segment-routing-03.txt and this work >> has considerably progressed in other WG. >>=20 >> Are you in favor of adopting = draft-sivabalan-pce-segment-routing-03.txt as a PCE WG document ? >>=20 >> Thanks. >>=20 >> JP and Julien. >>=20 >>=20 >>=20 >> _______________________________________________ >> Pce mailing list >> Pce@ietf.org >> https://www.ietf.org/mailman/listinfo/pce >=20 > _______________________________________________ > Pce mailing list > Pce@ietf.org > https://www.ietf.org/mailman/listinfo/pce --Apple-Mail=_9FA63404-10F7-428F-8A37-84C7E066D351 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii Dear = WG,

There is a clear consensus: authors please = resubmit as draft-ietf-pce-segment-routing-00.txt, with = no
other change than title, = date.

Thanks.

JP.
<= div>
On Sep 14, 2014, at 3:54 PM, JP Vasseur (jvasseur) = <jvasseur@cisco.com> = wrote:



Begin forwarded = message:

From: "JP Vasseur (jvasseur)" <jvasseur@cisco.com>
Subject: [Pce] Adopting of = draft-sivabalan-pce-segment-routing-03.txt as PCE WG = Document
Date: September 14, 2014 at 12:06:28 PM = GMT+2
To: "pce@ietf.org" <pce@ietf.org>

Dear WG,

We had several discussions showing a good consensus = adopting draft-sivabalan-pce-segment-routing-03.txt and this work
has = considerably progressed in other WG.

Are you in favor of adopting = draft-sivabalan-pce-segment-routing-03.txt as a PCE WG document = ?

Thanks.

JP and = Julien.



_______________________________________________
= Pce mailing list
Pce@ietf.org
https://www.ietf.org/ma= ilman/listinfo/pce

_____________= __________________________________
Pce mailing list
Pce@ietf.org
https://www.ietf.org/mail= man/listinfo/pce

= --Apple-Mail=_9FA63404-10F7-428F-8A37-84C7E066D351-- --Apple-Mail=_C9379C92-4C79-49C8-AD50-D4344F390A28 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="signature.asc" Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQEcBAEBCgAGBQJUG0WSAAoJEHBVWzpLl1MtMt8H/0mfHrgpmaM9ltnkf8m/z63H HueV99Kd6sMKWZK6/WR5GU0jFvtMK1OwML8Ly5+uLhY4u3DcsaZLboIhjJ3dbskR WYvSYf42XS8VCpN1SHUUDX2AsuDgen0k3goLGq7r7PDN9dZ5Ajx/cZL4CTQ4h7Mg XJonrYm4KRYJOl/0OPoebpgFB091p6VZPsXuPh37ZTZUYKnmVaw1I41YhnwrejMA o0t9k7t1uRAWcUQVokqLPBpnrgwXLcRKldTfXsIEt43PzvtIl82P9bGUmF7It4/0 StFRfkDuV3IAxpVg1Nzwcse4hwDNyCBpt/YvwHH2aehLDSxXXVDcgC6mkxtZN/o= =Eh02 -----END PGP SIGNATURE----- --Apple-Mail=_C9379C92-4C79-49C8-AD50-D4344F390A28-- From nobody Thu Sep 18 14:11:15 2014 Return-Path: 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 50C011A89B9; Thu, 18 Sep 2014 14:11:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.851 X-Spam-Level: X-Spam-Status: No, score=-4.851 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-1.652, 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 yF79z2McCjEQ; Thu, 18 Sep 2014 14:10:59 -0700 (PDT) Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B9F711A89B3; Thu, 18 Sep 2014 14:10:21 -0700 (PDT) Received: from 172.18.7.190 (EHLO lhreml402-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BJP41401; Thu, 18 Sep 2014 21:10:20 +0000 (GMT) Received: from DFWEML703-CHM.china.huawei.com (10.193.5.130) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 18 Sep 2014 22:10:19 +0100 Received: from DFWEML706-CHM.china.huawei.com ([10.193.5.225]) by dfweml703-chm ([10.193.5.130]) with mapi id 14.03.0158.001; Thu, 18 Sep 2014 14:10:09 -0700 From: Leeyoung To: OSCAR GONZALEZ DE DIOS , "pce@ietf.org" , "pce-chairs@ietf.org" Thread-Topic: Ask for early allocation of code-points of draft-ietf-pce-gmpls-pcep-extensions Thread-Index: AQHP0z9aZo3N6pvB8kObsAPNomK3jpwHYzoQ Date: Thu, 18 Sep 2014 21:10:08 +0000 Message-ID: <7AEB3D6833318045B4AE71C2C87E8E1729C375F5@dfweml706-chm> References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.47.140.156] Content-Type: multipart/alternative; boundary="_000_7AEB3D6833318045B4AE71C2C87E8E1729C375F5dfweml706chm_" MIME-Version: 1.0 X-CFilter-Loop: Reflected Archived-At: http://mailarchive.ietf.org/arch/msg/pce/c8OPn-DBurt4A-uY_lsBiFdTWBA Subject: Re: [Pce] Ask for early allocation of code-points of draft-ietf-pce-gmpls-pcep-extensions X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Sep 2014 21:11:07 -0000 --_000_7AEB3D6833318045B4AE71C2C87E8E1729C375F5dfweml706chm_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I support the early allocation of code points in the said draft. Young From: Pce [mailto:pce-bounces@ietf.org] On Behalf Of OSCAR GONZALEZ DE DIOS Sent: Thursday, September 18, 2014 7:52 AM To: pce@ietf.org; pce-chairs@ietf.org Subject: [Pce] Ask for early allocation of code-points of draft-ietf-pce-gm= pls-pcep-extensions Dear PCE WG chairs, PCErs, The document draft-ietf-pce-gmpls-pcep-extensions has been stable for a whi= le and it is near LC completion (the document started in 2010). There are e= arly implementations of the draft. In my opinion, it is of high value to ha= ve early allocated values to support such implementations. Authors of draft-ietf-pce-gmpls-pcep-extensions would like to request IAN= A the early allocation of the code-points included in draft-ietf-pce-gmpls-= pcep-extensions. We would like to ask PCErs if they see necessary the early allocation of co= de points in draft-ietf-pce-gmpls-pcep-extensions. Best Regards, =D3scar ________________________________ Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, pu= ede contener informaci=F3n privilegiada o confidencial y es para uso exclus= ivo de la persona o entidad de destino. Si no es usted. el destinatario ind= icado, queda notificado de que la lectura, utilizaci=F3n, divulgaci=F3n y/o= copia sin autorizaci=F3n puede estar prohibida en virtud de la legislaci= =F3n vigente. Si ha recibido este mensaje por error, le rogamos que nos lo = comunique inmediatamente por esta misma v=EDa y proceda a su destrucci=F3n. The information contained in this transmission is privileged and confidenti= al information intended only for the use of the individual or entity named = above. If the reader of this message is not the intended recipient, you are= hereby notified that any dissemination, distribution or copying of this co= mmunication is strictly prohibited. If you have received this transmission = in error, do not read it. Please immediately reply to the sender that you h= ave received this communication in error and then delete it. Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat=E1rio= , pode conter informa=E7=E3o privilegiada ou confidencial e =E9 para uso ex= clusivo da pessoa ou entidade de destino. Se n=E3o =E9 vossa senhoria o des= tinat=E1rio indicado, fica notificado de que a leitura, utiliza=E7=E3o, div= ulga=E7=E3o e/ou c=F3pia sem autoriza=E7=E3o pode estar proibida em virtude= da legisla=E7=E3o vigente. Se recebeu esta mensagem por erro, rogamos-lhe = que nos o comunique imediatamente por esta mesma via e proceda a sua destru= i=E7=E3o --_000_7AEB3D6833318045B4AE71C2C87E8E1729C375F5dfweml706chm_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

I support the early alloc= ation of code points in the said draft.

 <= /p>

Young

 <= /p>

From: Pce [mai= lto:pce-bounces@ietf.org] On Behalf Of OSCAR GONZALEZ DE DIOS
Sent: Thursday, September 18, 2014 7:52 AM
To: pce@ietf.org; pce-chairs@ietf.org
Subject: [Pce] Ask for early allocation of code-points of draft-ietf= -pce-gmpls-pcep-extensions

 

Dear PCE WG chairs, PCErs,<= o:p>

 

The document draft-iet= f-pce-gmpls-pcep-extensions has been stable for a while and it is near LC c= ompletion (the document started in 2010). There are early implementations of the draft. In my opinion, it is of high value to have early allocated v= alues to support such implementations.  

 

 Authors of  draf= t-ietf-pce-gmpls-pcep-extensions would like to request IANA the early alloc= ation of the code-points included in draft-ietf-pce-gmpls-pcep-extensi= ons. 

 

 

We would like to ask P= CErs if they see necessary the early allocation of code points in draft-iet= f-pce-gmpls-pcep-extensions. 

 

Best Regards,

 

=D3scar

 

 

 


Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, pu= ede contener informaci=F3n privilegiada o confidencial y es para uso exclus= ivo de la persona o entidad de destino. Si no es usted. el destinatario ind= icado, queda notificado de que la lectura, utilizaci=F3n, divulgaci=F3n y/o copia sin autorizaci=F3n puede e= star prohibida en virtud de la legislaci=F3n vigente. Si ha recibido este m= ensaje por error, le rogamos que nos lo comunique inmediatamente por esta m= isma v=EDa y proceda a su destrucci=F3n.

The information contained in this transmission is privileged and confidenti= al information intended only for the use of the individual or entity named = above. If the reader of this message is not the intended recipient, you are= hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If y= ou have received this transmission in error, do not read it. Please immedia= tely reply to the sender that you have received this communication in error= and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat=E1rio= , pode conter informa=E7=E3o privilegiada ou confidencial e =E9 para uso ex= clusivo da pessoa ou entidade de destino. Se n=E3o =E9 vossa senhoria o des= tinat=E1rio indicado, fica notificado de que a leitura, utiliza=E7=E3o, divulga=E7=E3o e/ou c=F3pia sem autoriza=E7=E3o p= ode estar proibida em virtude da legisla=E7=E3o vigente. Se recebeu esta me= nsagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mes= ma via e proceda a sua destrui=E7=E3o<= /o:p>

--_000_7AEB3D6833318045B4AE71C2C87E8E1729C375F5dfweml706chm_-- From nobody Thu Sep 18 14:39:05 2014 Return-Path: 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 193DC1A6F34 for ; Thu, 18 Sep 2014 14:39:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.03 X-Spam-Level: X-Spam-Status: No, score=-3.03 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-1.652, 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 yC9hM3oHBJwf for ; Thu, 18 Sep 2014 14:38:58 -0700 (PDT) Received: from mail-oi0-x22e.google.com (mail-oi0-x22e.google.com [IPv6:2607:f8b0:4003:c06::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5B4331A6EFB for ; Thu, 18 Sep 2014 14:38:58 -0700 (PDT) Received: by mail-oi0-f46.google.com with SMTP id i138so988038oig.33 for ; Thu, 18 Sep 2014 14:38:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=8JWV71F8KbB7bimmxO5uJAaq34CnwAXlkpz47Cl5rW8=; b=pp30E08Q6MdQihKg+5VFWls+Zk6LmmFVfn7JjL8tbMoOEQInU6eRwe4NFu3LXTpMk1 vPLqoWIERVUE79CNgsuscWFCIk4XalLSSFE7Z6hFTMc+rsEWIcCSeptyHfGejCAIYPCX LfWqklvXq7F4Q7bUEiVEOR3oEoqHV60HRx+ySldc3uxPf5wvP4AYFgfaM0jTArtzpB6E PNSVTjeV9gKnmby92OIKI0gPLjjq4MpzPoha+girrL7RRt0htGmEaoYH2S1nY9OCP+S4 KpVm8b1ihZHFb2XaDrItcxuaRvOZto3PEbCnuVBUnBJR3WEMoJNNCFfKiCHFLxO7d92S 1E4w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=8JWV71F8KbB7bimmxO5uJAaq34CnwAXlkpz47Cl5rW8=; b=PcQRtSgNDkVXN0hd8MBJ7DQaCrTRhKH8YWs9GwBSIQFet0d5yI98d3xwwUx42jlZIY LFSbuj996gftAtzemdn/scS8iLN52dpekq1FPJUzFGt9hgsSIJkZiyzkYjmgNF3sccx9 fD4hHtribOfNNaRegpn1Erg1Mz2NzBvgjuy8YsnmB3r+qzpjAp504V6xGLSXxYWMUTNq MpGxMPekTC2eFuWZ8vA4Zt2pgJRb25qD/rKO22DN40TaNr6S4wPYwOwKfm/iyKcOnU4h 9UMlxp11CI538WtQnVmUcf6Z8V+Z2ZR+5teRLiUNb76KGRt5DSoFwbjfvis7qL0X4QXS XJ6Q== X-Gm-Message-State: ALoCoQnrhdZMok0PtzFUCR5QK2T0twx9ukOnVqnxKbOzaJbZJw1uhxM/+RMGtwBIMK0BZy3qSI0w MIME-Version: 1.0 X-Received: by 10.182.22.233 with SMTP id h9mr2015089obf.48.1411076337678; Thu, 18 Sep 2014 14:38:57 -0700 (PDT) Received: by 10.182.26.18 with HTTP; Thu, 18 Sep 2014 14:38:57 -0700 (PDT) In-Reply-To: <8ed250570d734ce48d2afd971231dc1c@BN1PR05MB358.namprd05.prod.outlook.com> References: <70E9F53F-3A40-4CC6-924B-9BA229FD84AA@cisco.com> <23CE718903A838468A8B325B80962F9B865F8709@szxeml556-mbs.china.huawei.com> <8ed250570d734ce48d2afd971231dc1c@BN1PR05MB358.namprd05.prod.outlook.com> Date: Thu, 18 Sep 2014 14:38:57 -0700 Message-ID: From: Ina Minei To: Ramana Yarlagadda Content-Type: multipart/alternative; boundary=001a11c307bedbe7be05035dcff2 Archived-At: http://mailarchive.ietf.org/arch/msg/pce/K-PvGxv9ZUwvG4LFkH3rtQ7a0IQ Cc: "pce@ietf.org" Subject: Re: [Pce] minor discrepancy of Flags definition X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Sep 2014 21:39:03 -0000 --001a11c307bedbe7be05035dcff2 Content-Type: text/plain; charset=UTF-8 Thank you for catching this, we had fixed this in the base draft and not the initiation one, will be fixed in the next revision. Ina On Wed, Sep 17, 2014 at 8:01 AM, Ramana Yarlagadda wrote: > Hi, > > A noticed a minor discrepancy of Flags definition between the > draft-ietf-pce-pce-initiated-lsp-01 > And ietf-pce-stateful-pce > > Referring sec 5.3.1 of pce-pce-initiated-lsp-01, following is the > definition of Create flag. And has > Only two bits assigned for operational state. > > But the definition of the Flags has 3 bits for operational state in > section 7.3. of ietf-pce-stateful-pce. > > > 5.3.1. The Create flag > > The LSP object is defined in [I-D.ietf-pce-stateful-pce] and included > here for easy reference. > > 0 1 2 3 > 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | PLSP-ID | Flags |C| O|A|R|S|D| > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > // TLVs // > | | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > > > -regards > -ramana > > _______________________________________________ > Pce mailing list > Pce@ietf.org > https://www.ietf.org/mailman/listinfo/pce > --001a11c307bedbe7be05035dcff2 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Thank you for catching this, we had fixed this in the base= draft and not the initiation one, will be fixed in the next revision.=C2= =A0

Ina=C2=A0

=
On Wed, Sep 17, 2014 at 8:01 AM, Ramana Yarlagad= da <ryarlaga@juniper.net> wrote:
Hi,

A noticed a minor discrepancy of Flags definition between the draft-ietf-pc= e-pce-initiated-lsp-01
And ietf-pce-stateful-pce

Referring sec 5.3.1 of pce-pce-initiated-lsp-01, following is the definitio= n of Create flag. And has
Only two bits assigned for operational state.

But the definition of the Flags has 3 bits for operational state in section= 7.3. of ietf-pce-stateful-pce.


5.3.1.=C2=A0 The Create flag

=C2=A0 =C2=A0The LSP object is defined in [I-D.ietf-pce-stateful-pce] and i= ncluded
=C2=A0 =C2=A0here for easy reference.

=C2=A0 =C2=A0 =C2=A0 0=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A01=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A02=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A03
=C2=A0 =C2=A0 =C2=A0 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 = 7 8 9 0 1
=C2=A0 =C2=A0 =C2=A0+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+= -+-+-+-+-+
=C2=A0 =C2=A0 =C2=A0|=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 PLSP-ID=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |=C2=A0 = =C2=A0Flags |C|=C2=A0 O|A|R|S|D|
=C2=A0 =C2=A0 =C2=A0+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+= -+-+-+-+-+
=C2=A0 =C2=A0 =C2=A0//=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 TLVs=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0//
=C2=A0 =C2=A0 =C2=A0|=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0|
=C2=A0 =C2=A0 =C2=A0+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+= -+-+-+-+-+


-regards
-ramana

_______________________________________________
Pce mailing list
Pce@ietf.org
htt= ps://www.ietf.org/mailman/listinfo/pce

--001a11c307bedbe7be05035dcff2-- From nobody Fri Sep 19 01:08:47 2014 Return-Path: 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 5DCB81A000E; Fri, 19 Sep 2014 01:08:42 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.899 X-Spam-Level: X-Spam-Status: No, score=-101.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, USER_IN_WHITELIST=-100] 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 nzxU_CeeR8Et; Fri, 19 Sep 2014 01:08:40 -0700 (PDT) Received: from asmtp5.iomartmail.com (asmtp5.iomartmail.com [62.128.201.176]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 390C01A0008; Fri, 19 Sep 2014 01:08:39 -0700 (PDT) Received: from asmtp5.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id s8J88aoV015844; Fri, 19 Sep 2014 09:08:36 +0100 Received: from 950129200 (176-227-128-84.ip.skylogicnet.com [176.227.128.84]) (authenticated bits=0) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id s8J88OCA015815 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 19 Sep 2014 09:08:31 +0100 From: "Adrian Farrel" To: "'OSCAR GONZALEZ DE DIOS'" , , References: In-Reply-To: Date: Fri, 19 Sep 2014 09:08:22 +0100 Message-ID: <066201cfd3e0$e7f609b0$b7e21d10$@olddog.co.uk> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0663_01CFD3E9.49BE1B30" X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQGRX06BU2l2KiPM8x4mrtodZQb9LJyFAhPQ Content-Language: en-gb X-TM-AS-MML: disable X-TM-AS-Product-Ver: IMSS-7.1.0.1576-7.5.0.1018-20962.005 X-TM-AS-Result: No--34.414-10.0-31-10 X-imss-scan-details: No--34.414-10.0-31-10 X-TMASE-MatchedRID: pS5owHKhBO3I9SJ9WcdSP2zBijri5+RVI9yVcHNDU7baqqH/oHw+keHS 48bEb24iIGuayLYZcDFb80mRvrneums+z/6qjCvUJUmVCWU5R5w/fHa3mmABMmbrQ6i6Mw7Id5H 6Aix830B6pO9c4J2+KuZ8JvlBwtSZxAFMYEMzeR3idvCqqY53ae4dka7CjortnSPw4pGdVDxOUC pDW+Futo+Y4gbx+8qIN7NNZtQ0DOwBNjmzrIc5e1BUNeTDYq3aFzxbqiTgjrBfQHBCk/AHh9f1Z 3O1vUvEoXgCZGvtnCtTgkvj8BIj7ODUjX0RPZhTuTW7ZPvP2BqGCLB/Dx6yO9IMr4YcGjV7BSL8 5x29cntJegxmqCV6h81VZekeGYjzSACPWmsdsvjAm+zGFl/I+7UNNLAshGzQ3UYBl+UrtukPAWf /fn5/CWOnBcRfZEn5goA0jlRLL4vxVhA9+h9R2jCIlN/eSPB99yS7vvkvVUZb6PBUqmq+UtJcRy EeTRAk/xhjrnZS65Lc4WEWF9MBGYN1fMRjFu73vHKClHGjjr2503aEePxXRAAdFMC0xN/9PEIQ6 isyHHwcIfeRBwa7IXGaAlsiH8ZWQD5Pc//uvXZhykiAOWmptcJZ8YWz+6GhQiVvlCdqvr82woDw 3Vz2nvJ/Ds+a9Fb9T2oe1WZBk1vw9fqt/H+WcOXHtRY/KWhRK2Sy7D6K/XHkFix0anmKR5r3PeS N3eDl8NCNqKoORaHIcjYHiQsJRBadv+F8ucSI/Sl5cYQQGW+DddlymG7iS1cbfIj2Ta9sgC46py JTSnTrAsaMDDYvE8OnGqjuv48yIClWT8PZC7GeAiCmPx4NwGmRqNBHmBvenFK7VE/xL0lFGCd0S 0NCsuJcFpcI1r19bRBgfgpL1Ph2opVf8LXg0wpOBPb2qVYHaAZk0sEcY14= Archived-At: http://mailarchive.ietf.org/arch/msg/pce/Umllmy6vHQXDA9L33UC9dl1pQNM Subject: Re: [Pce] Ask for early allocation of code-points of draft-ietf-pce-gmpls-pcep-extensions X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: adrian@olddog.co.uk List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Sep 2014 08:08:42 -0000 This is a multipart message in MIME format. ------=_NextPart_000_0663_01CFD3E9.49BE1B30 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable The chairs might forgive me for jumping in since I am on a crusade... =20 I must ask, why are you asking for the code points that are in the draft already, and how will you handle the clash between those codepoints and = the ones already allocated and present in the registry? =20 I must also ask whether there are any plans to refresh the draft which = expired over a month ago. =20 Adrian =20 From: Pce [mailto:pce-bounces@ietf.org] On Behalf Of OSCAR GONZALEZ DE = DIOS Sent: 18 September 2014 13:52 To: pce@ietf.org; pce-chairs@ietf.org Subject: [Pce] Ask for early allocation of code-points of draft-ietf-pce-gmpls-pcep-extensions =20 Dear PCE WG chairs, PCErs, =20 The document draft-ietf-pce-gmpls-pcep-extensions has been stable for a = while and it is near LC completion (the document started in 2010). There are = early implementations of the draft. In my opinion, it is of high value to have = early allocated values to support such implementations. =20 =20 Authors of draft-ietf-pce-gmpls-pcep-extensions would like to request = IANA the early allocation of the code-points included in draft-ietf-pce-gmpls-pcep-extensions.=20 =20 We would like to ask PCErs if they see necessary the early allocation of = code points in draft-ietf-pce-gmpls-pcep-extensions.=20 =20 Best Regards, =20 =D3scar =20 =20 =20 _____ =20 Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, = puede contener informaci=F3n privilegiada o confidencial y es para uso = exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, = queda notificado de que la lectura, utilizaci=F3n, divulgaci=F3n y/o copia sin autorizaci=F3n puede estar prohibida en virtud de la legislaci=F3n = vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique = inmediatamente por esta misma v=EDa y proceda a su destrucci=F3n. The information contained in this transmission is privileged and = confidential information intended only for the use of the individual or entity named = above. If the reader of this message is not the intended recipient, you are = hereby notified that any dissemination, distribution or copying of this = communication is strictly prohibited. If you have received this transmission in error, = do not read it. Please immediately reply to the sender that you have received = this communication in error and then delete it. Esta mensagem e seus anexos se dirigem exclusivamente ao seu = destinat=E1rio, pode conter informa=E7=E3o privilegiada ou confidencial e =E9 para uso = exclusivo da pessoa ou entidade de destino. Se n=E3o =E9 vossa senhoria o destinat=E1rio = indicado, fica notificado de que a leitura, utiliza=E7=E3o, divulga=E7=E3o e/ou c=F3pia = sem autoriza=E7=E3o pode estar proibida em virtude da legisla=E7=E3o vigente. Se recebeu = esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma = via e proceda a sua destrui=E7=E3o ------=_NextPart_000_0663_01CFD3E9.49BE1B30 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

The chairs might forgive me = for jumping in since I am on a crusade...

 

I must ask, why are you asking = for the code points that are in the draft already, and how will you = handle the clash between those codepoints and the ones already allocated = and present in the registry?

 

I must also ask whether there = are any plans to refresh the draft which expired over a month = ago.

 

Adrian

 

From: Pce = [mailto:pce-bounces@ietf.org] On Behalf Of OSCAR GONZALEZ DE = DIOS
Sent: 18 September 2014 13:52
To: pce@ietf.org; = pce-chairs@ietf.org
Subject: [Pce] Ask for early allocation of = code-points of = draft-ietf-pce-gmpls-pcep-extensions

 

Dear PCE WG chairs, = PCErs,

 

The = document draft-ietf-pce-gmpls-pcep-extensions has been stable for a = while and it is near LC completion (the document started in 2010). There = are early implementations of the draft. In my opinion, it is of high = value to have early allocated values to support such implementations. =  

 

 Authors of =  draft-ietf-pce-gmpls-pcep-extensions would like to request IANA = the early allocation of the code-points included = in draft-ietf-pce-gmpls-pcep-extensions. 

=

 

We would like to ask = PCErs if they see necessary the early allocation of code points in = draft-ietf-pce-gmpls-pcep-extensions. 

 

Best = Regards,

 

=D3scar

 

 

 


Este mensaje y sus adjuntos = se dirigen exclusivamente a su destinatario, puede contener = informaci=F3n privilegiada o confidencial y es para uso exclusivo de la = persona o entidad de destino. Si no es usted. el destinatario indicado, = queda notificado de que la lectura, utilizaci=F3n, divulgaci=F3n y/o = copia sin autorizaci=F3n puede estar prohibida en virtud de la = legislaci=F3n vigente. Si ha recibido este mensaje por error, le rogamos = que nos lo comunique inmediatamente por esta misma v=EDa y proceda a su = destrucci=F3n.

The information contained in this transmission is = privileged and confidential information intended only for the use of the = individual or entity named above. If the reader of this message is not = the intended recipient, you are hereby notified that any dissemination, = distribution or copying of this communication is strictly prohibited. If = you have received this transmission in error, do not read it. Please = immediately reply to the sender that you have received this = communication in error and then delete it.

Esta mensagem e seus = anexos se dirigem exclusivamente ao seu destinat=E1rio, pode conter = informa=E7=E3o privilegiada ou confidencial e =E9 para uso exclusivo da = pessoa ou entidade de destino. Se n=E3o =E9 vossa senhoria o = destinat=E1rio indicado, fica notificado de que a leitura, = utiliza=E7=E3o, divulga=E7=E3o e/ou c=F3pia sem autoriza=E7=E3o pode = estar proibida em virtude da legisla=E7=E3o vigente. Se recebeu esta = mensagem por erro, rogamos-lhe que nos o comunique imediatamente por = esta mesma via e proceda a sua destrui=E7=E3o

------=_NextPart_000_0663_01CFD3E9.49BE1B30-- From nobody Fri Sep 19 03:02:16 2014 Return-Path: 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 5D26E1A0056; Fri, 19 Sep 2014 03:02:14 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.552 X-Spam-Level: X-Spam-Status: No, score=-3.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-1.652, 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 q7nQS2Vgxvzv; Fri, 19 Sep 2014 03:02:08 -0700 (PDT) Received: from smtpjc.telefonica.com (smtpjc.telefonica.com [81.47.204.76]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AFE521A005A; Fri, 19 Sep 2014 03:02:06 -0700 (PDT) Received: from smtpjc.telefonica.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 6C1692D0234; Fri, 19 Sep 2014 12:02:04 +0200 (CEST) Received: from ESTGVMSP114.EUROPE.telefonica.corp (unknown [10.92.4.9]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtpjc.telefonica.com (Postfix) with ESMTPS id 4E7042D022B; Fri, 19 Sep 2014 12:02:04 +0200 (CEST) Received: from emea01-am1-obe.outbound.protection.outlook.com (10.92.5.139) by tls.telefonica.com (10.93.6.55) with Microsoft SMTP Server (TLS) id 14.3.195.1; Fri, 19 Sep 2014 12:02:03 +0200 Received: from AMSPR06MB104.eurprd06.prod.outlook.com (10.242.90.155) by AMSPR06MB101.eurprd06.prod.outlook.com (10.242.90.146) with Microsoft SMTP Server (TLS) id 15.0.1029.13; Fri, 19 Sep 2014 10:02:02 +0000 Received: from AMSPR06MB104.eurprd06.prod.outlook.com ([169.254.8.131]) by AMSPR06MB104.eurprd06.prod.outlook.com ([169.254.8.131]) with mapi id 15.00.1034.003; Fri, 19 Sep 2014 10:02:02 +0000 From: OSCAR GONZALEZ DE DIOS To: Adrian Farrel , "pce@ietf.org" , "pce-chairs@ietf.org" Thread-Topic: [Pce] Ask for early allocation of code-points of draft-ietf-pce-gmpls-pcep-extensions Thread-Index: AQHP0z9aZo3N6pvB8kObsAPNomK3jpwIG0MAgABBSQA= Date: Fri, 19 Sep 2014 10:02:02 +0000 Message-ID: References: <066201cfd3e0$e7f609b0$b7e21d10$@olddog.co.uk> In-Reply-To: <066201cfd3e0$e7f609b0$b7e21d10$@olddog.co.uk> Accept-Language: es-ES, en-US Content-Language: es-ES X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.3.9.131030 x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [195.235.92.26] x-microsoft-antispam: BCL:0;PCL:0;RULEID:;UriScan:; x-forefront-prvs: 0339F89554 x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(189002)(40134004)(199003)(80022003)(81542003)(19300405004)(85852003)(76176999)(19625215002)(87936001)(2201001)(74502003)(97736003)(85306004)(54356999)(46102003)(19580395003)(83072002)(21056001)(101416001)(107046002)(83322001)(106116001)(105586002)(92726001)(15202345003)(81342003)(230783001)(106356001)(19580405001)(95666004)(79102003)(20776003)(77096002)(50986999)(64706001)(99396002)(92566001)(31966008)(107886001)(74662003)(2656002)(83506001)(90102001)(2501002)(66066001)(76482002)(16236675004)(36756003)(77982003)(4396001)(15975445006); DIR:OUT; SFP:1102; SCL:1; SRVR:AMSPR06MB101; H:AMSPR06MB104.eurprd06.prod.outlook.com; FPR:; MLV:sfv; PTR:InfoNoRecords; MX:1; A:1; LANG:en; Content-Type: multipart/alternative; boundary="_000_D041C9BC63A45oscargonzalezdediostelefonicacom_" MIME-Version: 1.0 X-OriginatorOrg: telefonica.com X-TM-AS-MML: No Archived-At: http://mailarchive.ietf.org/arch/msg/pce/rCxjiK_tf8isgA5kbJ92oP_g12o Subject: Re: [Pce] Ask for early allocation of code-points of draft-ietf-pce-gmpls-pcep-extensions X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Sep 2014 10:02:14 -0000 --_000_D041C9BC63A45oscargonzalezdediostelefonicacom_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi Adrian, We are asking for early allocation of code-points for draft-ietf-pce-gmpls-= pcep-extensions. In the draft there are several suggested values. Considera= tions: 1) At least one of the values clashes with existing RFC, so it is NOT valid= . As damage (a clash of one value) is already there, we want to solve it a= s soon as possible. It will imply a new code point for the clashed value. A= nd it will impact existing implementations. But, better fix it NOW and get = an stable code, rather than waiting. 2) There is NO GUARANTEE that the suggested values that do not have clash w= on't have a clash later. Some documents move faster than others, and then n= umbers are assigned and clash happens. Thus, in sake of stability, and give= n that there are early implementations that might get affected of such kind= of code-points move, we ask IANA to provide us codes that do not have clas= hes with existing RFCs, and that when other documents get their codes, they= do not clash with the ones of the draft (as it may still take a while to b= ecome RFC). I hope I am clear enough with what we are asking and why we are asking it. =D3scar De: 'Adrian Farrel' > Responder a: 'Adrian Farrel' > Fecha: viernes, 19 de septiembre de 2014 10:08 Para: Oscar Gonzalez de Dios >, "pce@ietf.org" >, "pce-chairs@ietf.org" > Asunto: RE: [Pce] Ask for early allocation of code-points of draft-ietf-pce= -gmpls-pcep-extensions The chairs might forgive me for jumping in since I am on a crusade... I must ask, why are you asking for the code points that are in the draft al= ready, and how will you handle the clash between those codepoints and the o= nes already allocated and present in the registry? I must also ask whether there are any plans to refresh the draft which expi= red over a month ago. Adrian From: Pce [mailto:pce-bounces@ietf.org] On Behalf Of OSCAR GONZALEZ DE DIOS Sent: 18 September 2014 13:52 To: pce@ietf.org; pce-chairs@ietf.org Subject: [Pce] Ask for early allocation of code-points of draft-ietf-pce-gm= pls-pcep-extensions Dear PCE WG chairs, PCErs, The document draft-ietf-pce-gmpls-pcep-extensions has been stable for a whi= le and it is near LC completion (the document started in 2010). There are e= arly implementations of the draft. In my opinion, it is of high value to ha= ve early allocated values to support such implementations. Authors of draft-ietf-pce-gmpls-pcep-extensions would like to request IAN= A the early allocation of the code-points included in draft-ietf-pce-gmpls-= pcep-extensions. We would like to ask PCErs if they see necessary the early allocation of co= de points in draft-ietf-pce-gmpls-pcep-extensions. Best Regards, =D3scar ________________________________ Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, pu= ede contener informaci=F3n privilegiada o confidencial y es para uso exclus= ivo de la persona o entidad de destino. Si no es usted. el destinatario ind= icado, queda notificado de que la lectura, utilizaci=F3n, divulgaci=F3n y/o= copia sin autorizaci=F3n puede estar prohibida en virtud de la legislaci= =F3n vigente. Si ha recibido este mensaje por error, le rogamos que nos lo = comunique inmediatamente por esta misma v=EDa y proceda a su destrucci=F3n. The information contained in this transmission is privileged and confidenti= al information intended only for the use of the individual or entity named = above. If the reader of this message is not the intended recipient, you are= hereby notified that any dissemination, distribution or copying of this co= mmunication is strictly prohibited. If you have received this transmission = in error, do not read it. Please immediately reply to the sender that you h= ave received this communication in error and then delete it. Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat=E1rio= , pode conter informa=E7=E3o privilegiada ou confidencial e =E9 para uso ex= clusivo da pessoa ou entidade de destino. Se n=E3o =E9 vossa senhoria o des= tinat=E1rio indicado, fica notificado de que a leitura, utiliza=E7=E3o, div= ulga=E7=E3o e/ou c=F3pia sem autoriza=E7=E3o pode estar proibida em virtude= da legisla=E7=E3o vigente. Se recebeu esta mensagem por erro, rogamos-lhe = que nos o comunique imediatamente por esta mesma via e proceda a sua destru= i=E7=E3o ________________________________ Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, pu= ede contener informaci=F3n privilegiada o confidencial y es para uso exclus= ivo de la persona o entidad de destino. Si no es usted. el destinatario ind= icado, queda notificado de que la lectura, utilizaci=F3n, divulgaci=F3n y/o= copia sin autorizaci=F3n puede estar prohibida en virtud de la legislaci= =F3n vigente. Si ha recibido este mensaje por error, le rogamos que nos lo = comunique inmediatamente por esta misma v=EDa y proceda a su destrucci=F3n. The information contained in this transmission is privileged and confidenti= al information intended only for the use of the individual or entity named = above. If the reader of this message is not the intended recipient, you are= hereby notified that any dissemination, distribution or copying of this co= mmunication is strictly prohibited. If you have received this transmission = in error, do not read it. Please immediately reply to the sender that you h= ave received this communication in error and then delete it. Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat=E1rio= , pode conter informa=E7=E3o privilegiada ou confidencial e =E9 para uso ex= clusivo da pessoa ou entidade de destino. Se n=E3o =E9 vossa senhoria o des= tinat=E1rio indicado, fica notificado de que a leitura, utiliza=E7=E3o, div= ulga=E7=E3o e/ou c=F3pia sem autoriza=E7=E3o pode estar proibida em virtude= da legisla=E7=E3o vigente. Se recebeu esta mensagem por erro, rogamos-lhe = que nos o comunique imediatamente por esta mesma via e proceda a sua destru= i=E7=E3o --_000_D041C9BC63A45oscargonzalezdediostelefonicacom_ Content-Type: text/html; charset="iso-8859-1" Content-ID: <9827E23D1CE7BF44829A962B46F999A4@eurprd06.prod.outlook.com> Content-Transfer-Encoding: quoted-printable
Hi Adrian,

We are= asking for early allocation of code-points for draft-ietf-pce-gmpls-p= cep-extensions. In the draft there are several suggested values. Considerat= ions:

1) At = least one of the values clashes with existing RFC, so it is NOT valid. &nbs= p;As damage (a clash of one value) is already there, we want to solve it as= soon as possible. It will imply a new code point for the clashed value. And it will impact existing implementations. = But, better fix it NOW and get an stable code, rather than waiting.

2) The= re is NO GUARANTEE that the suggested values that do not have clash wonR= 17;t have a clash later. Some documents move faster than others, and then n= umbers are assigned and clash happens. Thus, in sake of stability, and given that there are early implementations that = might get affected of such kind of code-points move, we ask IANA to provide= us codes that do not have clashes with existing RFCs, and that when other = documents get their codes, they do not clash with the ones of the draft (as it may still take a while to b= ecome RFC).
   

I hope= I am clear enough with what we are asking and why we are asking it.

=D3sca= r 


De: 'Adrian Farrel' <adrian@olddog.co.uk>
Responder a: 'Adrian Farrel' <adrian@olddog.co.uk>
Fecha: viernes, 19 de septiembre de= 2014 10:08
Para: Oscar Gonzalez de Dios <oscar.gonzalezdedios@t= elefonica.com>, "pce@ietf.org" <pce@ietf.org>, "pce-chairs@ietf.org"= <pce-chairs@ietf.org>
Asunto: RE: [Pce] Ask for early all= ocation of code-points of draft-ietf-pce-gmpls-pcep-extensions

The chairs might forgive me for jum= ping in since I am on a crusade...

 

I must ask, why are you asking for = the code points that are in the draft already, and how will you handle the = clash between those codepoints and the ones already allocated and present in the registry?

 

I must also ask whether there are a= ny plans to refresh the draft which expired over a month ago.

 

Adrian

 

From: Pce [mailto:pce-bounces@ietf.org] On Behalf Of OSCAR GONZALEZ DE DIOS
Sent: 18 September 2014 13:52
To: pce@ietf.org; pce-chairs@ietf.org
Subject: [Pce] Ask for early allocation of code-points of draft-ietf= -pce-gmpls-pcep-extensions

 

Dear PCE WG chairs, PCErs,=

 

The document draft-ietf-pce-gmpls-pcep-= extensions has been stable for a while and it is near LC completion (the do= cument started in 2010). There are early implementations of the draft. In my opinion, it is of high value to have e= arly allocated values to support such implementations.  

 

 Authors of  draft-ietf-pce-gmpls-= pcep-extensions would like to request IANA the early allocation of the code= -points included in draft-ietf-pce-gmpls-pcep-extensions. 

 

We would like to ask PCErs if they see = necessary the early allocation of code points in draft-ietf-pce-gmpls-pcep-= extensions. 

 

Best Regards,

 

=D3scar

 

 

 


Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, pu= ede contener informaci=F3n privilegiada o confidencial y es para uso exclus= ivo de la persona o entidad de destino. Si no es usted. el destinatario ind= icado, queda notificado de que la lectura, utilizaci=F3n, divulgaci=F3n y/o copia sin autorizaci=F3n puede e= star prohibida en virtud de la legislaci=F3n vigente. Si ha recibido este m= ensaje por error, le rogamos que nos lo comunique inmediatamente por esta m= isma v=EDa y proceda a su destrucci=F3n.

The information contained in this transmission is privileged and confidenti= al information intended only for the use of the individual or entity named = above. If the reader of this message is not the intended recipient, you are= hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If y= ou have received this transmission in error, do not read it. Please immedia= tely reply to the sender that you have received this communication in error= and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat=E1rio= , pode conter informa=E7=E3o privilegiada ou confidencial e =E9 para uso ex= clusivo da pessoa ou entidade de destino. Se n=E3o =E9 vossa senhoria o des= tinat=E1rio indicado, fica notificado de que a leitura, utiliza=E7=E3o, divulga=E7=E3o e/ou c=F3pia sem autoriza=E7=E3o p= ode estar proibida em virtude da legisla=E7=E3o vigente. Se recebeu esta me= nsagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mes= ma via e proceda a sua destrui=E7=E3o



Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, pu= ede contener informaci=F3n privilegiada o confidencial y es para uso exclus= ivo de la persona o entidad de destino. Si no es usted. el destinatario ind= icado, queda notificado de que la lectura, utilizaci=F3n, divulgaci=F3n y/o copia sin autorizaci=F3n puede e= star prohibida en virtud de la legislaci=F3n vigente. Si ha recibido este m= ensaje por error, le rogamos que nos lo comunique inmediatamente por esta m= isma v=EDa y proceda a su destrucci=F3n.

The information contained in this transmission is privileged and confidenti= al information intended only for the use of the individual or entity named = above. If the reader of this message is not the intended recipient, you are= hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If y= ou have received this transmission in error, do not read it. Please immedia= tely reply to the sender that you have received this communication in error= and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat=E1rio= , pode conter informa=E7=E3o privilegiada ou confidencial e =E9 para uso ex= clusivo da pessoa ou entidade de destino. Se n=E3o =E9 vossa senhoria o des= tinat=E1rio indicado, fica notificado de que a leitura, utiliza=E7=E3o, divulga=E7=E3o e/ou c=F3pia sem autoriza=E7=E3o p= ode estar proibida em virtude da legisla=E7=E3o vigente. Se recebeu esta me= nsagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mes= ma via e proceda a sua destrui=E7=E3o
 --_000_D041C9BC63A45oscargonzalezdediostelefonicacom_-- From nobody Fri Sep 19 06:19:16 2014 Return-Path: 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 564DA1A0166; Fri, 19 Sep 2014 06:19:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 EfoihxXKC7mh; Fri, 19 Sep 2014 06:19:11 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 221BD1A0158; Fri, 19 Sep 2014 06:19:11 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: Liaison Statement Management Tool To: glenn.parsons@ericsson.com X-Test-IDTracker: no X-IETF-IDTracker: 5.6.2.p6 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20140919131911.29133.16225.idtracker@ietfa.amsl.com> Date: Fri, 19 Sep 2014 06:19:11 -0700 Archived-At: http://mailarchive.ietf.org/arch/msg/pce/Hry8tDblpcbzq0GoFIQNumWUgpk Cc: pce@ietf.org, jpv@cisco.com Subject: [Pce] New Liaison Statement, "IETF PCE WG's Response to Liaision from IEEE 802.1 on August 11" X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Sep 2014 13:19:13 -0000 Title: IETF PCE WG's Response to Liaision from IEEE 802.1 on August 11 Submission Date: 2014-09-19 URL of the IETF Web page: http://datatracker.ietf.org/liaison/1352/ From: Path Computation Element (Julien Meuric ) To: IEEE 802.1 (glenn.parsons@ericsson.com) Cc: jpv@cisco.com,adrian@olddog.co.uk,akatlas@gmail.com,pce@ietf.org,Eric.Gray@Ericsson.com Response Contact: Technical Contact: Purpose: In response Referenced liaison: Liaison from IEEE 802.1 to IETF PCE WG (http://datatracker.ietf.org/liaison/1344/) Body: Thank you for your recent liaison about the potential use of PCE in your 802.1 work. We are pleased to hear that the technology developed within the IETF may have broader applicability. We would be pleased to receive liaisons from you about work that involves PCE and will bring any documents you send us to the attention of the PCE working group for participants to review and send feedback direct to the relevant part of 802.1. We would, of course, also be happy to answer any questions concerning how the PCE communication Protocol works and how the PCE architecture hangs together. As you will notice from the IANA registry for PCEP (https://www.iana.org/assignments/pcep/pcep.xhtml) code points can be allocated predominately only through the process called "IETF Review". Please see RFC 5226 for a full definition of this process, but in summary it requires the publication of an RFC that has IETF consensus. Therefore, if you identify the need for protocol extensions to PCEP in support of your work, the best approach will be to bring the requirements to the IETF in the form of an Internet-Draft and then to work within the PCE working group to develop the solution mechanisms (i.e., protocol extensions). This will ensure that any modifications to the protocol are consistent with the way the protocol was designed to work, and that there are no problems allocating the necessary code points. Looking forward to hearing more about this work, JP Vasseur and Julien Meuric (PCE Working Group Chairs) Attachments: No document has been attached From nobody Mon Sep 22 06:35:16 2014 Return-Path: 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 50F7F1A1ADC for ; Mon, 22 Sep 2014 06:35:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.1 X-Spam-Level: X-Spam-Status: No, score=-0.1 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=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 2DJX9kuw4d-1 for ; Mon, 22 Sep 2014 06:35:08 -0700 (PDT) Received: from mail-yk0-x229.google.com (mail-yk0-x229.google.com [IPv6:2607:f8b0:4002:c07::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 84EBA1A1AE8 for ; Mon, 22 Sep 2014 06:35:07 -0700 (PDT) Received: by mail-yk0-f169.google.com with SMTP id 10so1099034ykt.14 for ; Mon, 22 Sep 2014 06:35:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=T06/v7eFmUKOs8nI/jTR0ao9Kp/AHj9/3F3UF/PaFns=; b=l0zCJJrYePawgUp6WQTrF/9f4wc0yb00tyADpg+XXq5EiELVv9w3ACJHY9xRiUAqGK A4ONv09cgsCT0AXKvRNgvVd0KZHLY2OKM5hXRNgEsXq8Oi4rBPJUIcENQMYBHG89oOOO 5PjFaY8PITRUGewAIAQ/OPIlOEzRFqcuJL7tPTUH/IXMu/cTMQEj3ovxRBg51pIPHbvH w/FrDpuB8Fr3ULSrtZTqwTsxjMfh60DqET4HTEYihpx3DYNuUwsMhgoqx0qfuIrTKPJX YaYySv36OHuQZGZTuTNVlADOb2XQVly70eV+Gi22fCC+bdZypj7S/6NLCOe2Sgcf9e/n TKCw== MIME-Version: 1.0 X-Received: by 10.236.121.44 with SMTP id q32mr26841806yhh.55.1411392906658; Mon, 22 Sep 2014 06:35:06 -0700 (PDT) Received: by 10.170.90.85 with HTTP; Mon, 22 Sep 2014 06:35:06 -0700 (PDT) In-Reply-To: References: Date: Mon, 22 Sep 2014 09:35:06 -0400 Message-ID: From: Mohan Nanduri To: "JP Vasseur (jvasseur)" Content-Type: multipart/alternative; boundary=20cf300e512fd708ad0503a7845d Archived-At: http://mailarchive.ietf.org/arch/msg/pce/ZKkoQ02gFTAiVYx1zX8Wcp4V6Sg Cc: "pce@ietf.org" Subject: Re: [Pce] Adopting of draft-sivabalan-pce-segment-routing-03.txt as PCE WG Document X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Sep 2014 13:35:13 -0000 --20cf300e512fd708ad0503a7845d Content-Type: text/plain; charset=UTF-8 Support. Cheers, -Mohan On Sun, Sep 14, 2014 at 6:06 AM, JP Vasseur (jvasseur) wrote: > Dear WG, > > We had several discussions showing a good consensus adopting > draft-sivabalan-pce-segment-routing-03.txt and this work > has considerably progressed in other WG. > > Are you in favor of adopting draft-sivabalan-pce-segment-routing-03.txt as > a PCE WG document ? > > Thanks. > > JP and Julien. > > > > > _______________________________________________ > Pce mailing list > Pce@ietf.org > https://www.ietf.org/mailman/listinfo/pce > > --20cf300e512fd708ad0503a7845d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Support.

Cheers,
-Mohan

On Sun, Sep 14, 2014 = at 6:06 AM, JP Vasseur (jvasseur) <jvasseur@cisco.com> wrot= e:
Dear WG,

We had several discussions showing a good consensus adopting draft-sivabala= n-pce-segment-routing-03.txt and this work
has considerably progressed in other WG.

Are you in favor of adopting draft-sivabalan-pce-segment-routing-03.txt as = a PCE WG document ?

Thanks.

JP and Julien.




_______________________________________________
Pce mailing list
Pce@ietf.org
htt= ps://www.ietf.org/mailman/listinfo/pce


--20cf300e512fd708ad0503a7845d-- From nobody Mon Sep 22 08:07:54 2014 Return-Path: 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 D6AA41A1AFE for ; Mon, 22 Sep 2014 08:07:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.367 X-Spam-Level: X-Spam-Status: No, score=-2.367 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_LOW=-0.7, 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 odkJA9mxktVa for ; Mon, 22 Sep 2014 08:07:45 -0700 (PDT) Received: from mx0a-00082601.pphosted.com (mx0a-00082601.pphosted.com [67.231.145.42]) by ietfa.amsl.com (Postfix) with ESMTP id 6F75B1A1A87 for ; Mon, 22 Sep 2014 08:07:45 -0700 (PDT) Received: from pps.filterd (m0004346 [127.0.0.1]) by mx0a-00082601.pphosted.com (8.14.5/8.14.5) with SMTP id s8MF47nW005860 for ; Mon, 22 Sep 2014 08:07:44 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=fb.com; h=message-id : date : from : mime-version : to : subject : references : in-reply-to : content-type : content-transfer-encoding; s=facebook; bh=LplEm7UenJGoL7EK2r18XoDqZKmV5b/npojr7e33ghs=; b=WrGhRTAsgv/fklNJORox9/t+pkdn+LAizWfSuc4zkdrPcIre1FruCBaSBj4E2Rfesgk1 ZE3KFQb/K3MCoDuU3zZjUfVUi4gxyjew/ipU+63zrMmqNzhOOKMy9/GMwZEIR97PNYvY kbbNHDuO9Hp+KMfsGA19K0msNI1DJEmxpYM= Received: from mail.thefacebook.com (mailwest.thefacebook.com [173.252.71.148]) by mx0a-00082601.pphosted.com with ESMTP id 1pgu62unpx-3 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK) for ; Mon, 22 Sep 2014 08:07:44 -0700 Received: from [172.20.17.71] (192.168.16.4) by mail.thefacebook.com (192.168.16.14) with Microsoft SMTP Server (TLS) id 14.3.195.1; Mon, 22 Sep 2014 08:07:43 -0700 Message-ID: <54203B3E.3050405@fb.com> Date: Mon, 22 Sep 2014 09:07:42 -0600 From: Ebben Aries MIME-Version: 1.0 To: References: In-Reply-To: Content-Type: text/plain; charset="windows-1252"; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: [192.168.16.4] X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.12.52, 1.0.28, 0.0.0000 definitions=2014-09-22_01:2014-09-19,2014-09-21,1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=fb_default_notspam policy=fb_default score=0 kscore.is_bulkscore=3.52723406038535e-12 kscore.compositescore=0 circleOfTrustscore=83.392 compositescore=0.999779233484434 urlsuspect_oldscore=0.999779233484434 suspectscore=32 recipient_domain_to_sender_totalscore=0 phishscore=0 bulkscore=0 kscore.is_spamscore=0 recipient_to_sender_totalscore=0 recipient_domain_to_sender_domain_totalscore=10424 rbsscore=0.999779233484434 spamscore=0 recipient_to_sender_domain_totalscore=0 urlsuspectscore=0.9 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1402240000 definitions=main-1409220143 X-FB-Internal: deliver Archived-At: http://mailarchive.ietf.org/arch/msg/pce/TrZ3oMSVCbZ5Kql1jrggKOALzqQ Subject: Re: [Pce] Adopting of draft-sivabalan-pce-segment-routing-03.txt as PCE WG Document X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Sep 2014 15:07:52 -0000 support On 09/14/2014 04:06 AM, JP Vasseur (jvasseur) wrote: > Dear WG, > > We had several discussions showing a good consensus adopting draft-sivabalan-pce-segment-routing-03.txt and this work > has considerably progressed in other WG. > > Are you in favor of adopting draft-sivabalan-pce-segment-routing-03.txt as a PCE WG document ? > > Thanks. > > JP and Julien. > > > > > > _______________________________________________ > Pce mailing list > Pce@ietf.org > https://urldefense.proofpoint.com/v1/url?u=https://www.ietf.org/mailman/listinfo/pce&k=ZVNjlDMF0FElm4dQtryO4A%3D%3D%0A&r=GJQFPrZyyh453ywaGV%2FvoQ%3D%3D%0A&m=PqoUJwkAGDuIloyrQ8tNdt8zbgEUxJ4ZYdj6DsdElaE%3D%0A&s=b165daa2bfce627d2c91588c03aaa6ee663472f092169de02b0d91e594efd0ba > From nobody Mon Sep 22 15:41:07 2014 Return-Path: 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 17B021A6F2C for ; Mon, 22 Sep 2014 15:41:06 -0700 (PDT) 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, 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 QP6GsmCCIYpF for ; Mon, 22 Sep 2014 15:41:04 -0700 (PDT) Received: from mail-yh0-x229.google.com (mail-yh0-x229.google.com [IPv6:2607:f8b0:4002:c01::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AEDDB1A1AAD for ; Mon, 22 Sep 2014 15:41:04 -0700 (PDT) Received: by mail-yh0-f41.google.com with SMTP id b6so2361849yha.0 for ; Mon, 22 Sep 2014 15:41:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=sDccupEJTNhp3xmkDZ9aagcWWYBg2Sx7iulGi0J8nUY=; b=UdkLKMEHCj7o3KpR76UzBxe5P/SMAamcknH4ae5ov3/8fA/4N6lW9NvbTbvdSM70/Z gP2NUvL67R+h907CatRGatZwJj+ssN0ivT1t3Tq5dUPDSm4+INuiRgZjV1wlLXKbln+j f2yyG5tbKYQLtXfzQQcq0IG1QZMJzOJzmxrN48lUU1uBRBkDZDWf8wR/cYLjiMiu+vOS EW643lpzj7upAepeeMACqaQEJ4ERVU1VrA0+bCgHbWA8pF73OW9S0hhmDRrMMdKs6inu SnEGG+LracuEx8TjHmOyjcPuSkcGErarcDdxpuEU6ZDb57t5QcGzZX1/tUjmrggetPS1 OF2g== MIME-Version: 1.0 X-Received: by 10.236.124.143 with SMTP id x15mr5200625yhh.67.1411425663984; Mon, 22 Sep 2014 15:41:03 -0700 (PDT) Received: by 10.170.90.85 with HTTP; Mon, 22 Sep 2014 15:41:03 -0700 (PDT) In-Reply-To: <70E9F53F-3A40-4CC6-924B-9BA229FD84AA@cisco.com> References: <70E9F53F-3A40-4CC6-924B-9BA229FD84AA@cisco.com> Date: Mon, 22 Sep 2014 18:41:03 -0400 Message-ID: From: Mohan Nanduri To: "JP Vasseur (jvasseur)" Content-Type: multipart/alternative; boundary=20cf303bf60a542a8f0503af2529 Archived-At: http://mailarchive.ietf.org/arch/msg/pce/MqJgmJChpC_FwcSW7dgpWdAZTcA Cc: "pce@ietf.org" Subject: Re: [Pce] Adoption of draft-sivabalan-pce-lsp-setup-type-02.txt as a PCE WG Document X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Sep 2014 22:41:06 -0000 --20cf303bf60a542a8f0503af2529 Content-Type: text/plain; charset=UTF-8 Support. Cheers, -Mohan On Sun, Sep 14, 2014 at 6:06 AM, JP Vasseur (jvasseur) wrote: > Dear WG, > > We had several discussions showing a good consensus adopting > draft-sivabalan-pce-lsp-setup-type-02.txt and this work > has considerably progressed in other WG. > > Are you in favor of adopting draft-sivabalan-pce-lsp-setup-type-02.txt as > a PCE WG document ? > > Thanks. > > JP and Julien. > > _______________________________________________ > Pce mailing list > Pce@ietf.org > https://www.ietf.org/mailman/listinfo/pce > > --20cf303bf60a542a8f0503af2529 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Support.

Cheers,
-Mohan

On Sun= , Sep 14, 2014 at 6:06 AM, JP Vasseur (jvasseur) <jvasseur@cisco.com&= gt; wrote:
Dear WG,

We had several discussions showing a good consensus adopting draft-sivabala= n-pce-lsp-setup-type-02.txt and this work
has considerably progressed in other WG.

Are you in favor of adopting draft-sivabalan-pce-lsp-setup-type-02.txt as a= PCE WG document ?

Thanks.

JP and Julien.

_______________________________________________
Pce mailing list
Pce@ietf.org
htt= ps://www.ietf.org/mailman/listinfo/pce


--20cf303bf60a542a8f0503af2529-- From nobody Tue Sep 23 03:14:09 2014 Return-Path: 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 A26D31A701E; Tue, 23 Sep 2014 03:14:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 aJvm659z8uXW; Tue, 23 Sep 2014 03:14:02 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 43C5B1A7008; Tue, 23 Sep 2014 03:14:02 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 5.6.3 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20140923101402.24888.67987.idtracker@ietfa.amsl.com> Date: Tue, 23 Sep 2014 03:14:02 -0700 Archived-At: http://mailarchive.ietf.org/arch/msg/pce/-hABoDzZtT_l05Wwa4JuG2ZfLFg Cc: pce@ietf.org Subject: [Pce] I-D Action: draft-ietf-pce-pcep-mib-10.txt X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Sep 2014 10:14:03 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Path Computation Element Working Group of the IETF. Title : Path Computation Element Communications Protocol (PCEP) Management Information Base (MIB) Module Authors : Agrahara Kiran Koushik Emile Stephan Quintin Zhao Daniel King Jonathan Hardwick Filename : draft-ietf-pce-pcep-mib-10.txt Pages : 64 Date : 2014-09-23 Abstract: This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects for modeling of Path Computation Element communications Protocol (PCEP) for communications between a Path Computation Client (PCC) and a Path Computation Element (PCE), or between two PCEs. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-pce-pcep-mib/ There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-pce-pcep-mib-10 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=draft-ietf-pce-pcep-mib-10 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/ From nobody Tue Sep 23 03:22:23 2014 Return-Path: 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 B31E61A701E for ; Tue, 23 Sep 2014 03:22:20 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.687 X-Spam-Level: X-Spam-Status: No, score=-2.687 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.786, 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 X9YB7KKv87TO for ; Tue, 23 Sep 2014 03:22:17 -0700 (PDT) Received: from ENFIRHETS1.metaswitch.com (enfirhets1.metaswitch.com [192.91.191.166]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0F0A81A1A8A for ; Tue, 23 Sep 2014 03:22:17 -0700 (PDT) Received: from ENFICSCAS1.datcon.co.uk (172.18.4.13) by ENFIRHETS1.metaswitch.com (172.18.209.22) with Microsoft SMTP Server (TLS) id 14.3.195.1; Tue, 23 Sep 2014 11:22:07 +0100 Received: from ENFICSMBX1.datcon.co.uk ([fe80::d5d5:c683:a3be:3a19]) by ENFICSCAS1.datcon.co.uk ([fe80::3d12:12a9:26af:c7%11]) with mapi id 14.03.0195.001; Tue, 23 Sep 2014 11:22:15 +0100 From: Jonathan Hardwick To: Adrian Farrel Thread-Topic: [Pce] I-D Action: draft-ietf-pce-pcep-mib-10.txt Thread-Index: AQHP1xcz8l07oX4PsEKU12b42aJWl5wOgKNQ Date: Tue, 23 Sep 2014 10:22:14 +0000 Message-ID: <09CE6C3BE5E1EA40B987BF5F25D8DDBAFDCCA976@ENFICSMBX1.datcon.co.uk> Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.18.10.155] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/pce/9sOywdSgJqh9N0iM3ZGddGeivac Cc: "pce@ietf.org" Subject: [Pce] FW: I-D Action: draft-ietf-pce-pcep-mib-10.txt X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Sep 2014 10:22:20 -0000 Adrian This version of the PCEP MIB addresses your recent comments. Thanks again = for your input. Cheers Jon -----Original Message----- From: Pce [mailto:pce-bounces@ietf.org] On Behalf Of internet-drafts@ietf.o= rg Sent: 23 September 2014 11:14 To: i-d-announce@ietf.org Cc: pce@ietf.org Subject: [Pce] I-D Action: draft-ietf-pce-pcep-mib-10.txt A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Path Computation Element Working Group of= the IETF. Title : Path Computation Element Communications Protocol = (PCEP) Management Information Base (MIB) Module Authors : Agrahara Kiran Koushik Emile Stephan Quintin Zhao Daniel King Jonathan Hardwick Filename : draft-ietf-pce-pcep-mib-10.txt Pages : 64 Date : 2014-09-23 Abstract: This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects for modeling of Path Computation Element communications Protocol (PCEP) for communications between a Path Computation Client (PCC) and a Path Computation Element (PCE), or between two PCEs. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-pce-pcep-mib/ There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-pce-pcep-mib-10 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-pce-pcep-mib-10 Please note that it may take a couple of minutes from the time of submissio= n 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/ _______________________________________________ Pce mailing list Pce@ietf.org https://www.ietf.org/mailman/listinfo/pce From nobody Tue Sep 23 05:30:17 2014 Return-Path: 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 EC4BD1A8030; Tue, 23 Sep 2014 05:30:14 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -99.199 X-Spam-Level: X-Spam-Status: No, score=-99.199 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, USER_IN_WHITELIST=-100] 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 fa592YFxlow8; Tue, 23 Sep 2014 05:30:10 -0700 (PDT) Received: from asmtp3.iomartmail.com (asmtp3.iomartmail.com [62.128.201.159]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2618E1A7113; Tue, 23 Sep 2014 05:30:08 -0700 (PDT) Received: from asmtp3.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id s8NCU6HR017068; Tue, 23 Sep 2014 13:30:06 +0100 Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id s8NCU5u3017030 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 23 Sep 2014 13:30:05 +0100 From: "Adrian Farrel" To: "'OSCAR GONZALEZ DE DIOS'" , , References: <066201cfd3e0$e7f609b0$b7e21d10$@olddog.co.uk> In-Reply-To: Date: Tue, 23 Sep 2014 13:30:03 +0100 Message-ID: <051d01cfd72a$19d76ae0$4d8640a0$@olddog.co.uk> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_051E_01CFD732.7B9F2E40" X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQGRX06BU2l2KiPM8x4mrtodZQb9LAIm0ztxAb9btyicbGJbEA== Content-Language: en-gb X-TM-AS-MML: disable X-TM-AS-Product-Ver: IMSS-7.1.0.1576-7.5.0.1018-20970.007 X-TM-AS-Result: No--34.993-10.0-31-10 X-imss-scan-details: No--34.993-10.0-31-10 X-TMASE-MatchedRID: pS5owHKhBO1Cl9DEsHnSbXyX60mMab9IoKO8hENbdcuSXo7SF5Okb4zS 8a3MSlYlxdMDEDSgbA+gHjJby37o0n2NS+KnccOuU+OjsPhIWDg7Uh8Mo43jSVSOymiJfTYXOqn cbTLK4Xhanvfg6O3LwCaiCJNvVWCrYrhNWQv/6muVUcz8XpiS9ECrr/LkAQ46W/Kb+C9IfiJgvD erPvwAKL+csMPB2d+4KZ0OqQam3jq1sMSHsUAj4ARH1Nr7oERdGWAN/II9wcT3Ru3JrjJxKKLD5 e+3+4Hcynoxg+WKLWRAZ65Ta8ilTte+wTcw+4NCQpxiLlDD9FVC8qJD/WiiEeQydRUvl3QTdYZS O/EYTV7bg6o5EW5Wvtmp4ipRsurnKUe58oALvqwxVcFqdPEwQqKaxHqGRwkCVVuS1SVf7KPdyhY fGzFH0jMw+wBSWHN3QmabJK6KSrY/tAk1apUmVBK6EFc0lvV01yFgAZMasi/b41R9ITAz/m8HyV Sr6rJ2b1Tz7TBgFMFLO5gMEf4CaXg+Onbo3SKf0OdoO8pGssEz9B6orInyEq9Kn9Q3XUnqkTGhn jr2Kq9v7uSNt0YhMKZVCCl//NaCDXeruc+k2gx7nAGljbg/duUHrNdVVmqpfKnN0ncxnUroWX4o GwInXeZeCe70+X61ZsYgNo9yTsCSiNUIz7wlblZ0E+oA5pdVM/Xrz6lKsoL4JyR+b5tvoMNsx6m gbAHnqi/rtnceb+9k6iBybZ4VLlhqetUIrMthuQz4l+l24lYbbiqcGIoZv22Cz6PgUjeEDHn+8v 6/lTQh9Hvpadqd4XHgtjAx7vkIqoPJAu0CyhGeAiCmPx4NwGmRqNBHmBvenFK7VE/xL0lFGCd0S 0NCskQgrJ2X38jht3ji2nsYvq2MGHOyS3Diye26b0cMXoTGsBTJSD2iAW0= Archived-At: http://mailarchive.ietf.org/arch/msg/pce/TBoVjF6wxnQmvoZKe_p0TWh5yyk Subject: Re: [Pce] Ask for early allocation of code-points of draft-ietf-pce-gmpls-pcep-extensions X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: adrian@olddog.co.uk List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Sep 2014 12:30:15 -0000 This is a multipart message in MIME format. ------=_NextPart_000_051E_01CFD732.7B9F2E40 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I completely understand why you are asking. And I support that given the implementations and assuming that the I-D is sufficiently stable. =20 I do not understand what you asking :-( =20 draft-ietf-pce-gmpls-pcep-extensions has expired. The IANA cannot make = early allocations for it. The old version of draft-ietf-pce-gmpls-pcep-extensions contains = specific code points that IANA cannot allocate (as you observe). =20 What you need to do is... 1. Update the IANA section of the draft so that it is clean 2. Refresh the draft 3. Confirm with the chairs that this version is stable and meets other requirements of 7120 4. Ask the chairs for early allocation (and then they will confirm with = me) 5. Update the I-D (again) once the code points have been assigned 6. Remove all explicit, unassigned code points from other I-Ds you = co-author 7. Make a solemn vow never to put unassigned code points in an I-D =20 Cheers, Adrian =20 From: OSCAR GONZALEZ DE DIOS = [mailto:oscar.gonzalezdedios@telefonica.com]=20 Sent: 19 September 2014 11:02 To: Adrian Farrel; pce@ietf.org; pce-chairs@ietf.org Subject: Re: [Pce] Ask for early allocation of code-points of draft-ietf-pce-gmpls-pcep-extensions =20 Hi Adrian, =20 We are asking for early allocation of code-points for draft-ietf-pce-gmpls-pcep-extensions. In the draft there are several = suggested values. Considerations: =20 1) At least one of the values clashes with existing RFC, so it is NOT = valid. As damage (a clash of one value) is already there, we want to solve it as = soon as possible. It will imply a new code point for the clashed value. And it = will impact existing implementations. But, better fix it NOW and get an = stable code, rather than waiting. =20 2) There is NO GUARANTEE that the suggested values that do not have = clash won=92t have a clash later. Some documents move faster than others, and then = numbers are assigned and clash happens. Thus, in sake of stability, and given that = there are early implementations that might get affected of such kind of = code-points move, we ask IANA to provide us codes that do not have clashes with existing = RFCs, and that when other documents get their codes, they do not clash with the = ones of the draft (as it may still take a while to become RFC). =20 =20 I hope I am clear enough with what we are asking and why we are asking = it. =20 =D3scar=20 =20 =20 De: 'Adrian Farrel' Responder a: 'Adrian Farrel' Fecha: viernes, 19 de septiembre de 2014 10:08 Para: Oscar Gonzalez de Dios , "pce@ietf.org" , "pce-chairs@ietf.org" = Asunto: RE: [Pce] Ask for early allocation of code-points of draft-ietf-pce-gmpls-pcep-extensions =20 The chairs might forgive me for jumping in since I am on a crusade... =20 I must ask, why are you asking for the code points that are in the draft already, and how will you handle the clash between those codepoints and = the ones already allocated and present in the registry? =20 I must also ask whether there are any plans to refresh the draft which = expired over a month ago. =20 Adrian =20 From: Pce [mailto:pce-bounces@ietf.org] On Behalf Of OSCAR GONZALEZ DE = DIOS Sent: 18 September 2014 13:52 To: pce@ietf.org; pce-chairs@ietf.org Subject: [Pce] Ask for early allocation of code-points of draft-ietf-pce-gmpls-pcep-extensions =20 Dear PCE WG chairs, PCErs, =20 The document draft-ietf-pce-gmpls-pcep-extensions has been stable for a = while and it is near LC completion (the document started in 2010). There are = early implementations of the draft. In my opinion, it is of high value to have = early allocated values to support such implementations. =20 =20 Authors of draft-ietf-pce-gmpls-pcep-extensions would like to request = IANA the early allocation of the code-points included in draft-ietf-pce-gmpls-pcep-extensions.=20 =20 We would like to ask PCErs if they see necessary the early allocation of = code points in draft-ietf-pce-gmpls-pcep-extensions.=20 =20 Best Regards, =20 =D3scar =20 =20 =20 _____ =20 Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, = puede contener informaci=F3n privilegiada o confidencial y es para uso = exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, = queda notificado de que la lectura, utilizaci=F3n, divulgaci=F3n y/o copia sin autorizaci=F3n puede estar prohibida en virtud de la legislaci=F3n = vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique = inmediatamente por esta misma v=EDa y proceda a su destrucci=F3n. The information contained in this transmission is privileged and = confidential information intended only for the use of the individual or entity named = above. If the reader of this message is not the intended recipient, you are = hereby notified that any dissemination, distribution or copying of this = communication is strictly prohibited. If you have received this transmission in error, = do not read it. Please immediately reply to the sender that you have received = this communication in error and then delete it. Esta mensagem e seus anexos se dirigem exclusivamente ao seu = destinat=E1rio, pode conter informa=E7=E3o privilegiada ou confidencial e =E9 para uso = exclusivo da pessoa ou entidade de destino. Se n=E3o =E9 vossa senhoria o destinat=E1rio = indicado, fica notificado de que a leitura, utiliza=E7=E3o, divulga=E7=E3o e/ou c=F3pia = sem autoriza=E7=E3o pode estar proibida em virtude da legisla=E7=E3o vigente. Se recebeu = esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma = via e proceda a sua destrui=E7=E3o =20 _____ =20 Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, = puede contener informaci=F3n privilegiada o confidencial y es para uso = exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, = queda notificado de que la lectura, utilizaci=F3n, divulgaci=F3n y/o copia sin autorizaci=F3n puede estar prohibida en virtud de la legislaci=F3n = vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique = inmediatamente por esta misma v=EDa y proceda a su destrucci=F3n. The information contained in this transmission is privileged and = confidential information intended only for the use of the individual or entity named = above. If the reader of this message is not the intended recipient, you are = hereby notified that any dissemination, distribution or copying of this = communication is strictly prohibited. If you have received this transmission in error, = do not read it. Please immediately reply to the sender that you have received = this communication in error and then delete it. Esta mensagem e seus anexos se dirigem exclusivamente ao seu = destinat=E1rio, pode conter informa=E7=E3o privilegiada ou confidencial e =E9 para uso = exclusivo da pessoa ou entidade de destino. Se n=E3o =E9 vossa senhoria o destinat=E1rio = indicado, fica notificado de que a leitura, utiliza=E7=E3o, divulga=E7=E3o e/ou c=F3pia = sem autoriza=E7=E3o pode estar proibida em virtude da legisla=E7=E3o vigente. Se recebeu = esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma = via e proceda a sua destrui=E7=E3o ------=_NextPart_000_051E_01CFD732.7B9F2E40 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

I completely understand why you are asking. And I = support that given the implementations and assuming that the I-D is = sufficiently stable.

 

I do not understand what you asking = :-(

 

draft-ietf-pce-gmpls-pcep-extensions has expired. = The IANA cannot make early allocations for it.

The old version of = draft-ietf-pce-gmpls-pcep-extensions contains specific code points that = IANA cannot allocate (as you observe).

 

What you need to do is...

1. Update the IANA section of the draft so that it = is clean

2. Refresh the draft

3. Confirm with the chairs that this version is = stable and meets other requirements of 7120

4. Ask the chairs for early allocation (and then = they will confirm with me)

5. Update the I-D (again) once the code points = have been assigned

6. Remove all explicit, unassigned code points = from other I-Ds you co-author

7. Make a solemn vow never to put unassigned code = points in an I-D

 

Cheers,

Adrian

 

From: OSCAR GONZALEZ DE = DIOS [mailto:oscar.gonzalezdedios@telefonica.com]
Sent: 19 = September 2014 11:02
To: Adrian Farrel; pce@ietf.org; = pce-chairs@ietf.org
Subject: Re: [Pce] Ask for early = allocation of code-points of = draft-ietf-pce-gmpls-pcep-extensions

 

Hi = Adrian,

 

We are asking for early = allocation of code-points for draft-ietf-pce-gmpls-pcep-extensions. = In the draft there are several suggested values. = Considerations:

 

1) At least one of the values = clashes with existing RFC, so it is NOT valid.  As damage (a clash = of one value) is already there, we want to solve it as soon as possible. = It will imply a new code point for the clashed value. And it will impact = existing implementations. But, better fix it NOW and get an stable code, = rather than waiting.

 

2) There is NO GUARANTEE that = the suggested values that do not have clash won’t have a clash = later. Some documents move faster than others, and then numbers are = assigned and clash happens. Thus, in sake of stability, and given that = there are early implementations that might get affected of such kind of = code-points move, we ask IANA to provide us codes that do not have = clashes with existing RFCs, and that when other documents get their = codes, they do not clash with the ones of the draft (as it may still = take a while to become RFC).

  =  

 

I hope I am clear enough with = what we are asking and why we are asking = it.

 

=D3scar 

 

 

De: 'Adrian Farrel' <adrian@olddog.co.uk>
Res= ponder a: 'Adrian Farrel' <adrian@olddog.co.uk>
Fec= ha: viernes, 19 de septiembre de 2014 10:08
Para: Oscar = Gonzalez de Dios <oscar.gonzalezdedios@= telefonica.com>, "pce@ietf.org" <pce@ietf.org>, "pce-chairs@ietf.org" <pce-chairs@ietf.org>
Asu= nto: RE: [Pce] Ask for early allocation of code-points of = draft-ietf-pce-gmpls-pcep-extensions

 

The chairs might forgive me for jumping in since I am on a = crusade...

 

I must ask, why are you asking for the code points that are in the = draft already, and how will you handle the clash between those = codepoints and the ones already allocated and present in the = registry?

 

I must also ask whether there are any plans to refresh the draft = which expired over a month ago.

 

Adrian

 

From: Pce [mailto:pce-bounces@ietf.org] = On Behalf Of OSCAR GONZALEZ DE DIOS
Sent: 18 September = 2014 13:52
To: pce@ietf.org; pce-chairs@ietf.org
Subject= : [Pce] Ask for early allocation of code-points of = draft-ietf-pce-gmpls-pcep-extensions

 

Dear PCE WG chairs, PCErs,

 

The document draft-ietf-pce-gmpls-pcep-extensions has been stable = for a while and it is near LC completion (the document started in 2010). = There are early implementations of the draft. In my opinion, it is of = high value to have early allocated values to support such = implementations.  

 

 Authors of  draft-ietf-pce-gmpls-pcep-extensions would like = to request IANA the early allocation of the code-points included = in draft-ietf-pce-gmpls-pcep-extensions. 

 

We would like to ask PCErs if they see necessary the early = allocation of code points in = draft-ietf-pce-gmpls-pcep-extensions. 

 

Best Regards,

 

=D3scar

 

 

 

Este mensaje y sus adjuntos se dirigen exclusivamente a su = destinatario, puede contener informaci=F3n privilegiada o confidencial y = es para uso exclusivo de la persona o entidad de destino. Si no es = usted. el destinatario indicado, queda notificado de que la lectura, = utilizaci=F3n, divulgaci=F3n y/o copia sin autorizaci=F3n puede estar = prohibida en virtud de la legislaci=F3n vigente. Si ha recibido este = mensaje por error, le rogamos que nos lo comunique inmediatamente por = esta misma v=EDa y proceda a su destrucci=F3n.

The information = contained in this transmission is privileged and confidential = information intended only for the use of the individual or entity named = above. If the reader of this message is not the intended recipient, you = are hereby notified that any dissemination, distribution or copying of = this communication is strictly prohibited. If you have received this = transmission in error, do not read it. Please immediately reply to the = sender that you have received this communication in error and then = delete it.

Esta mensagem e seus anexos se dirigem exclusivamente = ao seu destinat=E1rio, pode conter informa=E7=E3o privilegiada ou = confidencial e =E9 para uso exclusivo da pessoa ou entidade de destino. = Se n=E3o =E9 vossa senhoria o destinat=E1rio indicado, fica notificado = de que a leitura, utiliza=E7=E3o, divulga=E7=E3o e/ou c=F3pia sem = autoriza=E7=E3o pode estar proibida em virtude da legisla=E7=E3o = vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o = comunique imediatamente por esta mesma via e proceda a sua = destrui=E7=E3o

 


Este mensaje y sus adjuntos = se dirigen exclusivamente a su destinatario, puede contener = informaci=F3n privilegiada o confidencial y es para uso exclusivo de la = persona o entidad de destino. Si no es usted. el destinatario indicado, = queda notificado de que la lectura, utilizaci=F3n, divulgaci=F3n y/o = copia sin autorizaci=F3n puede estar prohibida en virtud de la = legislaci=F3n vigente. Si ha recibido este mensaje por error, le rogamos = que nos lo comunique inmediatamente por esta misma v=EDa y proceda a su = destrucci=F3n.

The information contained in this transmission is = privileged and confidential information intended only for the use of the = individual or entity named above. If the reader of this message is not = the intended recipient, you are hereby notified that any dissemination, = distribution or copying of this communication is strictly prohibited. If = you have received this transmission in error, do not read it. Please = immediately reply to the sender that you have received this = communication in error and then delete it.

Esta mensagem e seus = anexos se dirigem exclusivamente ao seu destinat=E1rio, pode conter = informa=E7=E3o privilegiada ou confidencial e =E9 para uso exclusivo da = pessoa ou entidade de destino. Se n=E3o =E9 vossa senhoria o = destinat=E1rio indicado, fica notificado de que a leitura, = utiliza=E7=E3o, divulga=E7=E3o e/ou c=F3pia sem autoriza=E7=E3o pode = estar proibida em virtude da legisla=E7=E3o vigente. Se recebeu esta = mensagem por erro, rogamos-lhe que nos o comunique imediatamente por = esta mesma via e proceda a sua destrui=E7=E3o

------=_NextPart_000_051E_01CFD732.7B9F2E40-- From nobody Tue Sep 23 06:06:23 2014 Return-Path: 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 8FA021A8033 for ; Tue, 23 Sep 2014 06:06:21 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.67 X-Spam-Level: X-Spam-Status: No, score=-1.67 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, RP_MATCHES_RCVD=-0.786, SPF_SOFTFAIL=0.665] autolearn=no 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 DFTwiXYfUjFa for ; Tue, 23 Sep 2014 06:06:18 -0700 (PDT) Received: from p-mail1.rd.orange.com (p-mail1.rd.orange.com [195.101.245.15]) by ietfa.amsl.com (Postfix) with ESMTP id A24351A802E for ; Tue, 23 Sep 2014 06:06:17 -0700 (PDT) Received: from p-mail1.rd.orange.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 75D817D4011; Tue, 23 Sep 2014 15:06:16 +0200 (CEST) Received: from ftrdsmtp2.rd.francetelecom.fr (unknown [10.192.128.47]) by p-mail1.rd.orange.com (Postfix) with ESMTP id 6B6F27D4002; Tue, 23 Sep 2014 15:06:16 +0200 (CEST) Received: from ftrdmel10.rd.francetelecom.fr ([10.192.128.44]) by ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.4675); Tue, 23 Sep 2014 15:06:16 +0200 Received: from [10.193.71.69] ([10.193.71.69]) by ftrdmel10.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.4675); Tue, 23 Sep 2014 15:06:15 +0200 Message-ID: <54217047.7000206@orange.com> Date: Tue, 23 Sep 2014 15:06:15 +0200 From: Julien Meuric Organization: Orange User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.1 MIME-Version: 1.0 To: adrian@olddog.co.uk References: <066201cfd3e0$e7f609b0$b7e21d10$@olddog.co.uk> <051d01cfd72a$19d76ae0$4d8640a0$@olddog.co.uk> In-Reply-To: <051d01cfd72a$19d76ae0$4d8640a0$@olddog.co.uk> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit X-OriginalArrivalTime: 23 Sep 2014 13:06:15.0811 (UTC) FILETIME=[2863FD30:01CFD72F] Archived-At: http://mailarchive.ietf.org/arch/msg/pce/ZRWDIL1KFlkn8ej-tLu-S7SK64A Cc: pce@ietf.org Subject: Re: [Pce] Ask for early allocation of code-points of draft-ietf-pce-gmpls-pcep-extensions X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Sep 2014 13:06:21 -0000 Hi Adrian. I believe that when Oscar mentions "early allocation", he implicitly includes a refresh of the I-D as part of the process. This should address steps 1 and 2. Following a private discussion, 3-4-5 are being considered. Oscar's message below was a move to allow to judge the consensus as mentioned in RFC 7120. 6 and 7 are new requirements, I leave them to Oscar (and associated authors)... Regards, Julien Sep. 23, 2014 - Adrian Farrel: > I completely understand why you are asking. And I support that given the > implementations and assuming that the I-D is sufficiently stable. > > I do not understand what you asking :-( > > draft-ietf-pce-gmpls-pcep-extensions has expired. The IANA cannot make > early allocations for it. > > The old version of draft-ietf-pce-gmpls-pcep-extensions contains > specific code points that IANA cannot allocate (as you observe). > > What you need to do is... > > 1. Update the IANA section of the draft so that it is clean > > 2. Refresh the draft > > 3. Confirm with the chairs that this version is stable and meets other > requirements of 7120 > > 4. Ask the chairs for early allocation (and then they will confirm with me) > > 5. Update the I-D (again) once the code points have been assigned > > 6. Remove all explicit, unassigned code points from other I-Ds you co-author > > 7. Make a solemn vow never to put unassigned code points in an I-D > > Cheers, > > Adrian > > *From:*OSCAR GONZALEZ DE DIOS [mailto:oscar.gonzalezdedios@telefonica.com] > *Sent:* 19 September 2014 11:02 > *To:* Adrian Farrel; pce@ietf.org; pce-chairs@ietf.org > *Subject:* Re: [Pce] Ask for early allocation of code-points of > draft-ietf-pce-gmpls-pcep-extensions > > Hi Adrian, > > We are asking for early allocation of code-points > for draft-ietf-pce-gmpls-pcep-extensions. In the draft there are several > suggested values. Considerations: > > 1) At least one of the values clashes with existing RFC, so it is NOT > valid. As damage (a clash of one value) is already there, we want to > solve it as soon as possible. It will imply a new code point for the > clashed value. And it will impact existing implementations. But, better > fix it NOW and get an stable code, rather than waiting. > > 2) There is NO GUARANTEE that the suggested values that do not have > clash won’t have a clash later. Some documents move faster than others, > and then numbers are assigned and clash happens. Thus, in sake of > stability, and given that there are early implementations that might get > affected of such kind of code-points move, we ask IANA to provide us > codes that do not have clashes with existing RFCs, and that when other > documents get their codes, they do not clash with the ones of the draft > (as it may still take a while to become RFC). > > I hope I am clear enough with what we are asking and why we are asking it. > > Óscar > > *De: *'Adrian Farrel' > > *Responder a: *'Adrian Farrel' > > *Fecha: *viernes, 19 de septiembre de 2014 10:08 > *Para: *Oscar Gonzalez de Dios >, "pce@ietf.org > " >, > "pce-chairs@ietf.org " > > *Asunto: *RE: [Pce] Ask for early allocation of code-points of > draft-ietf-pce-gmpls-pcep-extensions > > The chairs might forgive me for jumping in since I am on a crusade... > > I must ask, why are you asking for the code points that are in the draft > already, and how will you handle the clash between those codepoints and > the ones already allocated and present in the registry? > > I must also ask whether there are any plans to refresh the draft which > expired over a month ago. > > Adrian > > *From:*Pce [mailto:pce-bounces@ietf.org] *On Behalf Of *OSCAR GONZALEZ > DE DIOS > *Sent:* 18 September 2014 13:52 > *To:* pce@ietf.org ; pce-chairs@ietf.org > > *Subject:* [Pce] Ask for early allocation of code-points of > draft-ietf-pce-gmpls-pcep-extensions > > Dear PCE WG chairs, PCErs, > > The document draft-ietf-pce-gmpls-pcep-extensions has been stable for a > while and it is near LC completion (the document started in 2010). There > are early implementations of the draft. In my opinion, it is of high > value to have early allocated values to support such implementations. > > Authors of draft-ietf-pce-gmpls-pcep-extensions would like to request > IANA the early allocation of the code-points included > in draft-ietf-pce-gmpls-pcep-extensions. > > We would like to ask PCErs if they see necessary the early allocation of > code points in draft-ietf-pce-gmpls-pcep-extensions. > > Best Regards, > > Óscar > > ------------------------------------------------------------------------ > > > Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, > puede contener información privilegiada o confidencial y es para uso > exclusivo de la persona o entidad de destino. Si no es usted. el > destinatario indicado, queda notificado de que la lectura, utilización, > divulgación y/o copia sin autorización puede estar prohibida en virtud > de la legislación vigente. Si ha recibido este mensaje por error, le > rogamos que nos lo comunique inmediatamente por esta misma vía y proceda > a su destrucción. > > The information contained in this transmission is privileged and > confidential information intended only for the use of the individual or > entity named above. If the reader of this message is not the intended > recipient, you are hereby notified that any dissemination, distribution > or copying of this communication is strictly prohibited. If you have > received this transmission in error, do not read it. Please immediately > reply to the sender that you have received this communication in error > and then delete it. > > Esta mensagem e seus anexos se dirigem exclusivamente ao seu > destinatário, pode conter informação privilegiada ou confidencial e é > para uso exclusivo da pessoa ou entidade de destino. Se não é vossa > senhoria o destinatário indicado, fica notificado de que a leitura, > utilização, divulgação e/ou cópia sem autorização pode estar proibida em > virtude da legislação vigente. Se recebeu esta mensagem por erro, > rogamos-lhe que nos o comunique imediatamente por esta mesma via e > proceda a sua destruição > > ------------------------------------------------------------------------ > > > Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, > puede contener información privilegiada o confidencial y es para uso > exclusivo de la persona o entidad de destino. Si no es usted. el > destinatario indicado, queda notificado de que la lectura, utilización, > divulgación y/o copia sin autorización puede estar prohibida en virtud > de la legislación vigente. Si ha recibido este mensaje por error, le > rogamos que nos lo comunique inmediatamente por esta misma vía y proceda > a su destrucción. > > The information contained in this transmission is privileged and > confidential information intended only for the use of the individual or > entity named above. If the reader of this message is not the intended > recipient, you are hereby notified that any dissemination, distribution > or copying of this communication is strictly prohibited. If you have > received this transmission in error, do not read it. Please immediately > reply to the sender that you have received this communication in error > and then delete it. > > Esta mensagem e seus anexos se dirigem exclusivamente ao seu > destinatário, pode conter informação privilegiada ou confidencial e é > para uso exclusivo da pessoa ou entidade de destino. Se não é vossa > senhoria o destinatário indicado, fica notificado de que a leitura, > utilização, divulgação e/ou cópia sem autorização pode estar proibida em > virtude da legislação vigente. Se recebeu esta mensagem por erro, > rogamos-lhe que nos o comunique imediatamente por esta mesma via e > proceda a sua destruição > > > > _______________________________________________ > Pce mailing list > Pce@ietf.org > https://www.ietf.org/mailman/listinfo/pce > From nobody Tue Sep 23 06:18:31 2014 Return-Path: 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 4D1861A8028; Tue, 23 Sep 2014 06:18:26 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.686 X-Spam-Level: X-Spam-Status: No, score=-2.686 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.786, 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 lBcApaaPI99U; Tue, 23 Sep 2014 06:18:21 -0700 (PDT) Received: from smtptc.telefonica.com (smtptc.telefonica.com [195.76.34.108]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 23FC61A7113; Tue, 23 Sep 2014 06:18:19 -0700 (PDT) Received: from smtptc.telefonica.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 67CAD8811E; Tue, 23 Sep 2014 15:18:17 +0200 (CEST) Received: from ESTGVMSP102.EUROPE.telefonica.corp (unknown [10.92.4.9]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtptc.telefonica.com (Postfix) with ESMTPS id 3FBB088111; Tue, 23 Sep 2014 15:18:17 +0200 (CEST) Received: from emea01-db3-obe.outbound.protection.outlook.com (10.92.5.139) by tls.telefonica.com (10.93.6.49) with Microsoft SMTP Server (TLS) id 14.3.195.1; Tue, 23 Sep 2014 15:18:16 +0200 Received: from AMSPR06MB104.eurprd06.prod.outlook.com (10.242.90.155) by AMSPR06MB101.eurprd06.prod.outlook.com (10.242.90.146) with Microsoft SMTP Server (TLS) id 15.0.1034.13; Tue, 23 Sep 2014 13:18:15 +0000 Received: from AMSPR06MB104.eurprd06.prod.outlook.com ([169.254.8.131]) by AMSPR06MB104.eurprd06.prod.outlook.com ([169.254.8.131]) with mapi id 15.00.1034.003; Tue, 23 Sep 2014 13:18:15 +0000 From: OSCAR GONZALEZ DE DIOS To: Adrian Farrel , "pce@ietf.org" , "pce-chairs@ietf.org" Thread-Topic: [Pce] Ask for early allocation of code-points of draft-ietf-pce-gmpls-pcep-extensions Thread-Index: AQHP0z9aZo3N6pvB8kObsAPNomK3jpwIG0MAgABBSQCABlEngIAAKZaAgAAFZ4A= Date: Tue, 23 Sep 2014 13:18:14 +0000 Message-ID: References: <066201cfd3e0$e7f609b0$b7e21d10$@olddog.co.uk> <051d01cfd72a$19d76ae0$4d8640a0$@olddog.co.uk> In-Reply-To: Accept-Language: es-ES, en-US Content-Language: es-ES X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.3.9.131030 x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [195.235.92.26] x-microsoft-antispam: BCL:0;PCL:0;RULEID:;SRVR:AMSPR06MB101; x-forefront-prvs: 0343AC1D30 x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(199003)(189002)(74502003)(4396001)(120916001)(66066001)(93886004)(85306004)(16236675004)(19580395003)(97736003)(10300001)(15975445006)(31966008)(20776003)(101416001)(36756003)(106356001)(15202345003)(19625215002)(19580405001)(83322001)(76482002)(107046002)(107886001)(86362001)(19300405004)(21056001)(64706001)(77096002)(95666004)(90102001)(46102003)(2656002)(105586002)(80022003)(2201001)(76176999)(87936001)(230783001)(54356999)(92566001)(50986999)(106116001)(2501002)(83506001)(85852003)(81342003)(74662003)(79102003)(77982003)(81542003)(83072002)(99396002)(92726001)(579004); DIR:OUT; SFP:1102; SCL:1; SRVR:AMSPR06MB101; H:AMSPR06MB104.eurprd06.prod.outlook.com; FPR:; MLV:sfv; PTR:InfoNoRecords; A:1; MX:1; LANG:en; Content-Type: multipart/alternative; boundary="_000_D0473F0F63F8Foscargonzalezdediostelefonicacom_" MIME-Version: 1.0 X-OriginatorOrg: telefonica.com X-TM-AS-MML: No Archived-At: http://mailarchive.ietf.org/arch/msg/pce/LHsw0dH4CxKmCCNS53ddqy8fspc Subject: [Pce] FW: Ask for early allocation of code-points of draft-ietf-pce-gmpls-pcep-extensions X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Sep 2014 13:18:26 -0000 --_000_D0473F0F63F8Foscargonzalezdediostelefonicacom_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Hi Adrian, all I completely understand why you are asking. And I support that given the im= plementations and assuming that the I-D is sufficiently stable. I do not understand what you asking :-( [Oscar] We asked the WG chairs advice on how to proceed with draft-ietf-pce= -gmpls-pcep-extensions and if we could request early allocation of code-poi= nts. PCE WG chairs told us, regarding the early allocation, that there was = not yet consensus on the matter. I was trying to build that consensus by a= sking in the PCE WG list if people considered necessary requesting early al= location, as early allocation needs per 7120 sufficient interest in the com= munity. draft-ietf-pce-gmpls-pcep-extensions has expired. The IANA cannot make ear= ly allocations for it. The old version of draft-ietf-pce-gmpls-pcep-extensions contains specific c= ode points that IANA cannot allocate (as you observe). [Oscar] We have a new version of draft-ietf-pce-gmpls-pcep-extensions ready= to submit addressing last call comments and all IANA values removed. What you need to do is... 1. Update the IANA section of the draft so that it is clean 2. Refresh the draft 3. Confirm with the chairs that this version is stable and meets other requ= irements of 7120 4. Ask the chairs for early allocation (and then they will confirm with me) 5. Update the I-D (again) once the code points have been assigned 6. Remove all explicit, unassigned code points from other I-Ds you co-autho= r 7. Make a solemn vow never to put unassigned code points in an I-D [Oscar] We will start with 1 & 2 (without values in IANA section). Cheers, Adrian Best Regards, Oscar From: OSCAR GONZALEZ DE DIOS [mailto:oscar.gonzalezdedios@telefonica.com] Sent: 19 September 2014 11:02 To: Adrian Farrel; pce@ietf.org; pce-chairs@ietf.org Subject: Re: [Pce] Ask for early allocation of code-points of draft-ietf-pc= e-gmpls-pcep-extensions Hi Adrian, We are asking for early allocation of code-points for draft-ietf-pce-gmpls-= pcep-extensions. In the draft there are several suggested values. Considera= tions: 1) At least one of the values clashes with existing RFC, so it is NOT valid= . As damage (a clash of one value) is already there, we want to solve it a= s soon as possible. It will imply a new code point for the clashed value. A= nd it will impact existing implementations. But, better fix it NOW and get = an stable code, rather than waiting. 2) There is NO GUARANTEE that the suggested values that do not have clash w= on=92t have a clash later. Some documents move faster than others, and then= numbers are assigned and clash happens. Thus, in sake of stability, and gi= ven that there are early implementations that might get affected of such ki= nd of code-points move, we ask IANA to provide us codes that do not have cl= ashes with existing RFCs, and that when other documents get their codes, th= ey do not clash with the ones of the draft (as it may still take a while to= become RFC). I hope I am clear enough with what we are asking and why we are asking it. =D3scar De: 'Adrian Farrel' > Responder a: 'Adrian Farrel' > Fecha: viernes, 19 de septiembre de 2014 10:08 Para: Oscar Gonzalez de Dios >, "pce@ietf.org" >, "pce-chairs@ietf.org" > Asunto: RE: [Pce] Ask for early allocation of code-points of draft-ietf-pce= -gmpls-pcep-extensions The chairs might forgive me for jumping in since I am on a crusade... I must ask, why are you asking for the code points that are in the draft al= ready, and how will you handle the clash between those codepoints and the o= nes already allocated and present in the registry? I must also ask whether there are any plans to refresh the draft which expi= red over a month ago. Adrian From: Pce [mailto:pce-bounces@ietf.org] On Behalf Of OSCAR GONZALEZ DE DIOS Sent: 18 September 2014 13:52 To: pce@ietf.org; pce-chairs@ietf.org Subject: [Pce] Ask for early allocation of code-points of draft-ietf-pce-gm= pls-pcep-extensions Dear PCE WG chairs, PCErs, The document draft-ietf-pce-gmpls-pcep-extensions has been stable for a whi= le and it is near LC completion (the document started in 2010). There are e= arly implementations of the draft. In my opinion, it is of high value to ha= ve early allocated values to support such implementations. Authors of draft-ietf-pce-gmpls-pcep-extensions would like to request IAN= A the early allocation of the code-points included in draft-ietf-pce-gmpls-= pcep-extensions. We would like to ask PCErs if they see necessary the early allocation of co= de points in draft-ietf-pce-gmpls-pcep-extensions. Best Regards, =D3scar ________________________________ Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, pu= ede contener informaci=F3n privilegiada o confidencial y es para uso exclus= ivo de la persona o entidad de destino. Si no es usted. el destinatario ind= icado, queda notificado de que la lectura, utilizaci=F3n, divulgaci=F3n y/o= copia sin autorizaci=F3n puede estar prohibida en virtud de la legislaci= =F3n vigente. Si ha recibido este mensaje por error, le rogamos que nos lo = comunique inmediatamente por esta misma v=EDa y proceda a su destrucci=F3n. The information contained in this transmission is privileged and confidenti= al information intended only for the use of the individual or entity named = above. If the reader of this message is not the intended recipient, you are= hereby notified that any dissemination, distribution or copying of this co= mmunication is strictly prohibited. If you have received this transmission = in error, do not read it. Please immediately reply to the sender that you h= ave received this communication in error and then delete it. Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat=E1rio= , pode conter informa=E7=E3o privilegiada ou confidencial e =E9 para uso ex= clusivo da pessoa ou entidade de destino. Se n=E3o =E9 vossa senhoria o des= tinat=E1rio indicado, fica notificado de que a leitura, utiliza=E7=E3o, div= ulga=E7=E3o e/ou c=F3pia sem autoriza=E7=E3o pode estar proibida em virtude= da legisla=E7=E3o vigente. Se recebeu esta mensagem por erro, rogamos-lhe = que nos o comunique imediatamente por esta mesma via e proceda a sua destru= i=E7=E3o ________________________________ Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, pu= ede contener informaci=F3n privilegiada o confidencial y es para uso exclus= ivo de la persona o entidad de destino. Si no es usted. el destinatario ind= icado, queda notificado de que la lectura, utilizaci=F3n, divulgaci=F3n y/o= copia sin autorizaci=F3n puede estar prohibida en virtud de la legislaci= =F3n vigente. Si ha recibido este mensaje por error, le rogamos que nos lo = comunique inmediatamente por esta misma v=EDa y proceda a su destrucci=F3n. The information contained in this transmission is privileged and confidenti= al information intended only for the use of the individual or entity named = above. If the reader of this message is not the intended recipient, you are= hereby notified that any dissemination, distribution or copying of this co= mmunication is strictly prohibited. If you have received this transmission = in error, do not read it. Please immediately reply to the sender that you h= ave received this communication in error and then delete it. Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat=E1rio= , pode conter informa=E7=E3o privilegiada ou confidencial e =E9 para uso ex= clusivo da pessoa ou entidade de destino. Se n=E3o =E9 vossa senhoria o des= tinat=E1rio indicado, fica notificado de que a leitura, utiliza=E7=E3o, div= ulga=E7=E3o e/ou c=F3pia sem autoriza=E7=E3o pode estar proibida em virtude= da legisla=E7=E3o vigente. Se recebeu esta mensagem por erro, rogamos-lhe = que nos o comunique imediatamente por esta mesma via e proceda a sua destru= i=E7=E3o ________________________________ Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, pu= ede contener informaci=F3n privilegiada o confidencial y es para uso exclus= ivo de la persona o entidad de destino. Si no es usted. el destinatario ind= icado, queda notificado de que la lectura, utilizaci=F3n, divulgaci=F3n y/o= copia sin autorizaci=F3n puede estar prohibida en virtud de la legislaci= =F3n vigente. Si ha recibido este mensaje por error, le rogamos que nos lo = comunique inmediatamente por esta misma v=EDa y proceda a su destrucci=F3n. The information contained in this transmission is privileged and confidenti= al information intended only for the use of the individual or entity named = above. If the reader of this message is not the intended recipient, you are= hereby notified that any dissemination, distribution or copying of this co= mmunication is strictly prohibited. If you have received this transmission = in error, do not read it. Please immediately reply to the sender that you h= ave received this communication in error and then delete it. Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat=E1rio= , pode conter informa=E7=E3o privilegiada ou confidencial e =E9 para uso ex= clusivo da pessoa ou entidade de destino. Se n=E3o =E9 vossa senhoria o des= tinat=E1rio indicado, fica notificado de que a leitura, utiliza=E7=E3o, div= ulga=E7=E3o e/ou c=F3pia sem autoriza=E7=E3o pode estar proibida em virtude= da legisla=E7=E3o vigente. Se recebeu esta mensagem por erro, rogamos-lhe = que nos o comunique imediatamente por esta mesma via e proceda a sua destru= i=E7=E3o --_000_D0473F0F63F8Foscargonzalezdediostelefonicacom_ Content-Type: text/html; charset="Windows-1252" Content-ID: <82672B43DA36E640B1ADE9300FB947A6@eurprd06.prod.outlook.com> Content-Transfer-Encoding: quoted-printable
Hi Adrian, all

I completely understand why you are= asking. And I support that given the implementations and assuming that the= I-D is sufficiently stable.

I do not und= erstand what you asking :-(

[Oscar] We asked the WG chairs advice on how to proceed with draft-iet= f-pce-gmpls-pcep-extensions and if we could request early allocation of cod= e-points. PCE WG chairs told us, regarding the early allocation, that there= was not yet consensus on the matter.  I was trying to build that consensus by asking in the PCE WG list if= people considered necessary requesting early allocation, as early allocati= on needs per 7120 sufficient interest in the community. 

 draft-ietf-pce-gmpls-pcep-extensions has expired. The IANA cannot make early allocations for it.

The old version of draft-ietf-pce-g= mpls-pcep-extensions contains specific code points that IANA cannot allocat= e (as you observe).

[Oscar] We have a new version of draft-ietf-pce-gmpls-pcep-extens= ions ready to submit addressing last call comments and all IANA values remo= ved.

 

What you need to do is...

1. Update the IANA section of the d= raft so that it is clean

2. Refresh the draft

3. Confirm with the chairs that thi= s version is stable and meets other requirements of 7120<= /p>

4. Ask the chairs for early allocat= ion (and then they will confirm with me)

5. Update the I-D (again) once the = code points have been assigned

6. Remove all explicit, unassigned = code points from other I-Ds you co-author

7. Make a solemn vow never to put u= nassigned code points in an I-D

 
[Oscar] We will start with 1 & 2 (without values in IANA section).=  
 

Cheers,

Adrian

Best Regards,

Oscar<= /div>

 

From: OSCAR GONZALEZ DE D= IOS [mailto:oscar.go= nzalezdedios@telefonica.com]
Sent: 19 September 2014 11:02
To: Adrian Farrel; pce@ietf.org;= pce-chairs@ietf.org
Subject: Re: [Pce] Ask for early allocation of code-points of draft-= ietf-pce-gmpls-pcep-extensions

 

Hi Adrian,

 

We are asking for early allocation of code-p= oints for draft-ietf-pce-gmpls-pcep-extensions. In the draft there are= several suggested values. Considerations:

 

1) At least one of the values clashes with e= xisting RFC, so it is NOT valid.  As damage (a clash of one value) is = already there, we want to solve it as soon as possible. It will imply a new code point for the clashed value. And it = will impact existing implementations. But, better fix it NOW and get an sta= ble code, rather than waiting.

 

2) There is NO GUARANTEE that the suggested = values that do not have clash won=92t have a clash later. Some documents mo= ve faster than others, and then numbers are assigned and clash happens. Thus, in sake of stability, and given that= there are early implementations that might get affected of such kind of co= de-points move, we ask IANA to provide us codes that do not have clashes wi= th existing RFCs, and that when other documents get their codes, they do not clash with the ones of the dr= aft (as it may still take a while to become RFC).

   

 

I hope I am clear enough with what we are as= king and why we are asking it.

 

=D3scar 

 

 

De: 'Adrian Farrel' <adrian@olddog.co.uk>
Responder a: 'Adrian Farrel' <adrian@olddog.co.uk>
Fecha: viernes, 19 de septiembre de 2014 10:08
Para: Oscar Gonzalez de Dios <oscar.gonzalezdedios@telefonica.com>, "pce@ietf.org" <pce@ietf.org>, "pce-chairs@ietf.org" <pce-chairs@ietf.org>
Asunto: RE: [Pce] Ask for early allocation of code-points of draft-i= etf-pce-gmpls-pcep-extensions

 

The chairs might forgive me for jum= ping in since I am on a crusade...<= /o:p>

 

I must ask, why are you asking for = the code points that are in the draft already, and how will you handle the = clash between those codepoints and the ones already allocated and present in the registry?

 

I must also ask whether there are a= ny plans to refresh the draft which expired over a month ago.

 

Adrian

 

From: Pce [mailto:pce-bounces@iet= f.org] On Behalf Of OSCAR GONZALEZ DE DIOS
Sent: 18 September 2014 13:52
To: pce@ietf.org; pce-chairs@ietf.org
Subject: [Pce] Ask for early allocation of code-points of draft-ietf= -pce-gmpls-pcep-extensions

 =

Dear PCE WG chairs, PCErs,

 

The document draft-ietf-pce-gmpls-pcep-= extensions has been stable for a while and it is near LC completion (the do= cument started in 2010). There are early implementations of the draft. In my opinion, it is of high value to have e= arly allocated values to support such implementations.  

 

 Authors of  draft-ietf-pce-gmpls-= pcep-extensions would like to request IANA the early allocation of the code= -points included in draft-ietf-pce-gmpls-pcep-extensions. =

 

We would like to ask PCErs if they see = necessary the early allocation of code points in draft-ietf-pce-gmpls-pcep-= extensions. 

 

Best Regards,

 

=D3scar

 

 

 


Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, pu= ede contener informaci=F3n privilegiada o confidencial y es para uso exclus= ivo de la persona o entidad de destino. Si no es usted. el destinatario ind= icado, queda notificado de que la lectura, utilizaci=F3n, divulgaci=F3n y/o copia sin autorizaci=F3n puede e= star prohibida en virtud de la legislaci=F3n vigente. Si ha recibido este m= ensaje por error, le rogamos que nos lo comunique inmediatamente por esta m= isma v=EDa y proceda a su destrucci=F3n.

The information contained in this transmission is privileged and confidenti= al information intended only for the use of the individual or entity named = above. If the reader of this message is not the intended recipient, you are= hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If y= ou have received this transmission in error, do not read it. Please immedia= tely reply to the sender that you have received this communication in error= and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat=E1rio= , pode conter informa=E7=E3o privilegiada ou confidencial e =E9 para uso ex= clusivo da pessoa ou entidade de destino. Se n=E3o =E9 vossa senhoria o des= tinat=E1rio indicado, fica notificado de que a leitura, utiliza=E7=E3o, divulga=E7=E3o e/ou c=F3pia sem autoriza=E7=E3o p= ode estar proibida em virtude da legisla=E7=E3o vigente. Se recebeu esta me= nsagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mes= ma via e proceda a sua destrui=E7=E3o

 


Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, pu= ede contener informaci=F3n privilegiada o confidencial y es para uso exclus= ivo de la persona o entidad de destino. Si no es usted. el destinatario ind= icado, queda notificado de que la lectura, utilizaci=F3n, divulgaci=F3n y/o copia sin autorizaci=F3n puede e= star prohibida en virtud de la legislaci=F3n vigente. Si ha recibido este m= ensaje por error, le rogamos que nos lo comunique inmediatamente por esta m= isma v=EDa y proceda a su destrucci=F3n.

The information contained in this transmission is privileged and confidenti= al information intended only for the use of the individual or entity named = above. If the reader of this message is not the intended recipient, you are= hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If y= ou have received this transmission in error, do not read it. Please immedia= tely reply to the sender that you have received this communication in error= and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat=E1rio= , pode conter informa=E7=E3o privilegiada ou confidencial e =E9 para uso ex= clusivo da pessoa ou entidade de destino. Se n=E3o =E9 vossa senhoria o des= tinat=E1rio indicado, fica notificado de que a leitura, utiliza=E7=E3o, divulga=E7=E3o e/ou c=F3pia sem autoriza=E7=E3o p= ode estar proibida em virtude da legisla=E7=E3o vigente. Se recebeu esta me= nsagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mes= ma via e proceda a sua destrui=E7=E3o



Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, pu= ede contener informaci=F3n privilegiada o confidencial y es para uso exclus= ivo de la persona o entidad de destino. Si no es usted. el destinatario ind= icado, queda notificado de que la lectura, utilizaci=F3n, divulgaci=F3n y/o copia sin autorizaci=F3n puede e= star prohibida en virtud de la legislaci=F3n vigente. Si ha recibido este m= ensaje por error, le rogamos que nos lo comunique inmediatamente por esta m= isma v=EDa y proceda a su destrucci=F3n.

The information contained in this transmission is privileged and confidenti= al information intended only for the use of the individual or entity named = above. If the reader of this message is not the intended recipient, you are= hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If y= ou have received this transmission in error, do not read it. Please immedia= tely reply to the sender that you have received this communication in error= and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat=E1rio= , pode conter informa=E7=E3o privilegiada ou confidencial e =E9 para uso ex= clusivo da pessoa ou entidade de destino. Se n=E3o =E9 vossa senhoria o des= tinat=E1rio indicado, fica notificado de que a leitura, utiliza=E7=E3o, divulga=E7=E3o e/ou c=F3pia sem autoriza=E7=E3o p= ode estar proibida em virtude da legisla=E7=E3o vigente. Se recebeu esta me= nsagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mes= ma via e proceda a sua destrui=E7=E3o
 --_000_D0473F0F63F8Foscargonzalezdediostelefonicacom_-- From nobody Mon Sep 29 04:55:06 2014 Return-Path: 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 9E25C1A873B; Mon, 29 Sep 2014 04:55:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 EeJRTETpqvIy; Mon, 29 Sep 2014 04:55:02 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id EDB941A875B; Mon, 29 Sep 2014 04:54:58 -0700 (PDT) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: The IESG To: IETF-Announce X-Test-IDTracker: no X-IETF-IDTracker: 5.6.3.p1 Auto-Submitted: auto-generated Precedence: bulk Sender: Message-ID: <20140929115458.21966.49314.idtracker@ietfa.amsl.com> Date: Mon, 29 Sep 2014 04:54:58 -0700 Archived-At: http://mailarchive.ietf.org/arch/msg/pce/YgfVrcrSb37OVsFLPJ57LIRGQ6c Cc: pce@ietf.org Subject: [Pce] Last Call: (Path Computation Element Communications Protocol (PCEP) Management Information Base (MIB) Module) to Proposed Standard X-BeenThere: pce@ietf.org X-Mailman-Version: 2.1.15 Reply-To: ietf@ietf.org List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Sep 2014 11:55:03 -0000 The IESG has received a request from the Path Computation Element WG (pce) to consider the following document: - 'Path Computation Element Communications Protocol (PCEP) Management Information Base (MIB) Module' as Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the ietf@ietf.org mailing lists by 2014-10-13. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. Abstract This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects for modeling of Path Computation Element communications Protocol (PCEP) for communications between a Path Computation Client (PCC) and a Path Computation Element (PCE), or between two PCEs. The file can be obtained via http://datatracker.ietf.org/doc/draft-ietf-pce-pcep-mib/ IESG discussion can be tracked via http://datatracker.ietf.org/doc/draft-ietf-pce-pcep-mib/ballot/ No IPR declarations have been submitted directly on this I-D.