I am not aware of any IPR applicable to this draft that should be disclosed
in accordance with IETF IPR rules.
Cheers
Jon
From: Hariharan Ananthakrishnan
Sent: 04 September 2020 22:08
To: slitk...@cisco.com; msiva...@gmail.com; jefftant.i...@gmail.com; Jonathan
Hardwick ; Mahend Negi
; c
I support publication.
Cheers
Jon
-Original Message-
From: Dhruv Dhody
Sent: 08 November 2019 16:07
To: pce@ietf.org
Subject: Re: [Pce] I-D Action: draft-ietf-pce-stateful-flags-00.txt
Hi WG,
As instructed by our AD, I-D has been posted with the file name change
-
I have read the document. It's straightforward and clear. I think it's ready to
be published.
Cheers
Jon
-Original Message-
From: Pce On Behalf Of Dhruv Dhody
Sent: 09 September 2019 12:05
To: pce@ietf.org
Cc: pce-chairs
Subject: Re: [Pce] WG LC for draft-farrel-pce-stateful-flags-01
I support adoption of this draft (as co-author).
The binding label provides a mechanism for interworking between separate MPLS
switching domains, which is an important consideration as SR is rolled out.
Extending PCEP with this capability is a logical and necessary step.
Cheers
Jon
I am not aware of any IPR applicable to this draft that should be disclosed in
accordance with IETF IPR rules.
Cheers
Jon
From: Hariharan Ananthakrishnan
Sent: 21 August 2019 04:40
To: Siva Sivabalan (msiva) ; cfils...@cisco.com;
jefftant.i...@gmail.com; Jonathan Hardwick ;
stef
Thanks Rakesh, sounds good to me.
Jon
From: Rakesh Gandhi
Sent: 21 June 2019 18:30
To: Jonathan Hardwick
Cc: rtg-...@ietf.org; rtg-...@ietf.org; pce@ietf.org;
draft-ietf-pce-stateful-pce-auto-bandwidth@ietf.org
Subject: Re: [Pce] Routing directorate review of
draft-ietf-pce-stateful-pce
Hi there
I have reviewed this draft for the routing directorate as part of preparing it
for IETF last call and IESG review.
I was familiar with this document from the time that I chaired the PCE working
group, but this was the first time I read it all the way through and paid
attention to all
I have just completed a second shepherd review of this document. For
reference, my first review can be found at the link below.
https://mailarchive.ietf.org/arch/msg/pce/kAw8SJX3uv5_gsW7Qa03Td0pBU4
I would like to pass a massive vote of thanks to the authors for reacting
brilliantly to my
-dra...@ietf.org
Sent: Tuesday, 12 February, 2019 10:53 AM
To: Wim Henderickx ; Siva Sivabalan
; Jonathan Hardwick ;
Jonathan Hardwick ; Jeff Tantsura
; Clarence Filsfils
Subject: New Version Notification for draft-ietf-pce-segment-routing-15.txt
NOTE: Message is from an external sender
A new
Hi Benjamin
As I was preparing the next revision of this document, I realised I'd forgotten
to reply to your email. (I thought I had replied, but I can find no evidence
that I did so!)
Anyway, I think we have converged. Please see my proposals below, and
apologies for my tardiness.
Cheers
Hi Alvaro
I'm sorry that it has taken longer than I thought to reply to your comments!
Please find our replies below. I will post an updated version of the document
as soon as I can.
Many thanks
Jon
--
DISCUSS:
of what you'd expect, I think the definition
is nevertheless clear as it is written.
Cheers
Jon
-Original Message-
From: Julien Meuric
Sent: Monday, 7 January, 2019 9:37 AM
To: Jeff Tantsura
Cc: Dhruv Dhody ; Jonathan Hardwick
; Martin Vigoureux
; The IESG ;
draft-ietf-pce-segment-
Thanks Warren - noted.
I have been in conference with my co-authors regarding Alvaro's comments. We
are close to having a complete reply.
My apologies for the delay.
Best regards
Jon
-Original Message-
From: Warren Kumari
Sent: Friday, 7 December, 2018 4:41 PM
To: The IESG
Cc:
Spencer,
I think it is as Adrian has described below (thanks Adrian). I will add the
reference to RFC 8413.
Best regards
Jon
-Original Message-
From: Adrian Farrel
Sent: Thursday, 6 December, 2018 2:49 PM
To: 'Spencer Dawkins' ; 'The IESG'
Cc: pce@ietf.org; pce-cha...@ietf.org;
Alissa
Thanks for your comment - sorry for the delay in replying.
> Section 8.4 strikes me as a little odd for an archival document -- presumably
> draft-ietf-pce-pcep-yang either will or will not include the listed items, so
> the recommendations will either be out-of-date or false once
>
Hi Martin
Sorry for the delayed response. Please find replies to your comments below.
Best regards
Jon
Could you elaborate on what you mean by: "or to perform a specific service on
the packet."
[Jon] I think it should say "specific function". Some examples of this can be
found in
Hi Benjamin
Sorry for the delayed response. Please find replies to your comments below.
Best regards
Jon
Abstract
This document specifies extensions to the Path
Computation Element Communication Protocol (PCEP) that allow a
stateful PCE to compute and initiate
Hi Alvaro
Many thanks for these comments. I have read them, but need to have a
discussion with my co-authors before I can answer them all. I hope to get back
to you with a full reply early next week.
Many thanks
Jon
-Original Message-
From: Alvaro Retana
Sent: Wednesday, 5
From: Jonathan Hardwick
Sent: Saturday, 13 October, 2018 9:47 PM
To: pce@ietf.org
Cc: draft-zhao-pce-pcep-extension-for-pce-control...@ietf.org;
pce-cha...@ietf.org
Subject: WG adoption poll for
draft-zhao-pce-pcep-extension-for-pce-controller-08
This is the start of a two week poll on making
This is the start of a two week poll on making
draft-zhao-pce-pcep-extension-for-pce-controller-08 a PCE working group
document.
https://datatracker.ietf.org/doc/draft-zhao-pce-pcep-extension-for-pce-controller/
Please review the draft and send an email to the list indicating "yes/support"
or
This poll ended a week ago, with a pretty limited response. The chairs will
discuss next steps with the authors.
Cheers
Jon
From: Jonathan Hardwick
Sent: Friday, 21 September, 2018 2:19 PM
To: pce@ietf.org; draft-zhang-pce-resource-shar...@ietf.org
Cc: pce-cha...@ietf.org
Subject: WG adoption
AM
To: Jonathan Hardwick ; pce@ietf.org; Dhruv
Dhody
Subject: RE: New Version Notification for draft-ietf-pce-segment-routing-13.txt
Thanks Jon for this update.
All my previous comments are handled.
I was preparing the shepherd report, could you update these -
(1) IDnits -
https
To: Wim Henderickx ; Siva Sivabalan
; Jonathan Hardwick ;
Jonathan Hardwick ; Jeff Tantsura
; Clarence Filsfils
Subject: New Version Notification for draft-ietf-pce-segment-routing-13.txt
A new version of I-D, draft-ietf-pce-segment-routing-13.txt
has been successfully submitted by Jon Hardwick
2:59 PM
To: Marina Fizgeer
Cc: pce@ietf.org; Siva Sivabalan (msiva) ; Clarence Filsfils
(cfilsfil) ; Jeff Tantsura ;
wim.henderi...@alcatel-lucent.com; Jonathan Hardwick
; Michael Gorokhovsky
; Alexander Vainshtein
; Alexander Ferdman
; ron.sday...@ecitele.com; Dhruv Dhody
Subject: Re
Dear authors of draft-ietf-pce-stateful-pce-p2mp,
Could you please send an email to the PCE mailing list saying whether you are
aware of any IPR that applies to draft-ietf-pce-stateful-pce-p2mp and, if so,
if it has been disclosed in compliance with IETF IPR rules? (See RFCs 3979,
4879, 3669
Hi all
This message begins a 2-week WG last call for
draft-ietf-pce-stateful-pce-p2mp-07.
https://datatracker.ietf.org/doc/draft-ietf-pce-stateful-pce-p2mp/
Please read the document and reply to the PCE mailing list, indicating whether
you believe this document is ready to be published or not
Jonathan Hardwick has requested publication of draft-ietf-pce-wson-rwa-ext-08
as Proposed Standard on behalf of the PCE working group.
Please verify the document's state at
https://datatracker.ietf.org/doc/draft-ietf-pce-wson-rwa-ext/
___
Pce mailing
Hi PCE WG!
This is the start of a two week poll on making
draft-zhang-pce-resource-sharing-07 a PCE working group document.
https://datatracker.ietf.org/doc/draft-zhang-pce-resource-sharing/
Please review the draft and send an email to the list indicating "yes/support"
or "no/do not support".
[mailto:michael.gorokhov...@ecitele.com]
Sent: Wednesday, August 15, 2018 5:33 PM
To: Jonathan Hardwick ; Marina Fizgeer
; Dhruv Dhody
Cc: pce@ietf.org; Siva Sivabalan (msiva) ; Clarence Filsfils
(cfilsfil) ; Jeff Tantsura ;
wim.henderi...@alcatel-lucent.com; Alexander Vainshtein
; Alexander
Jon
From: Marina Fizgeer [mailto:marina.fizg...@ecitele.com]
Sent: Wednesday, August 15, 2018 4:38 PM
To: Jonathan Hardwick ; Dhruv Dhody
Cc: pce@ietf.org; Siva Sivabalan (msiva) ; Clarence Filsfils
(cfilsfil) ; Jeff Tantsura ;
wim.henderi...@alcatel-lucent.com; Michael Gorokhovsky
; Alexander
Marina, Dhruv,
Please see below.
Cheers
Jon
From: Dhruv Dhody [mailto:dhruv.i...@gmail.com]
Sent: Wednesday, August 15, 2018 2:59 PM
To: Marina Fizgeer
Cc: pce@ietf.org; Siva Sivabalan (msiva) ; Clarence Filsfils
(cfilsfil) ; Jeff Tantsura ;
wim.henderi...@alcatel-lucent.com; Jonathan
Thanks for the review, Dhruv! I'll think about your comments and get back to
you SOON (possibly not until after my vacation next week).
Cheers
Jon
From: Dhruv Dhody [mailto:dhruv.dh...@huawei.com]
Sent: Thursday, August 9, 2018 12:36 PM
To: pce@ietf.org
Cc: pce-cha...@ietf.org;
uot;MSD exceeds the default for the PCEP session").
Thanks
Jon
-Original Message-
From: Aissaoui, Mustapha (Nokia - CA/Ottawa)
[mailto:mustapha.aissa...@nokia.com]
Sent: 29 June 2018 19:19
To: Jonathan Hardwick ; pce@ietf.org
Subject: RE: [Pce] FW: I-D Action: draft-ietf-pce-segment-ro
Hi Cyril
Many apologies for the delay – please see below.
Cheers
Jon
From: Pce [mailto:pce-boun...@ietf.org] On Behalf Of Cyril Margaria
Sent: 30 January 2018 16:49
To: Dhruv Dhody
Cc: pce@ietf.org
Subject: Re: [Pce] WG Last Call for draft-ietf-pce-segment-routing-11
Hi,
I have the
Hi Dhruv
My apologies for the delay. Please find my replies and comments below.
Cheers
Jon
-Original Message-
From: Pce [mailto:pce-boun...@ietf.org] On Behalf Of Dhruv Dhody
Sent: 30 January 2018 09:20
To: Julien Meuric ; pce@ietf.org
Subject: Re: [Pce] WG Last Call for
...@gmail.com;
martin.vigour...@nokia.com; Jonathan Hardwick
; julien.meu...@orange.com
Cc: dhruv.i...@gmail.com; pce@ietf.org; rfc-edi...@rfc-editor.org
Subject: [Editorial Errata Reported] RFC8233 (5389)
The following errata report has been submitted for RFC8233, "Extensions to the
Path Comput
Hi PCE WG!
This is the start of a two week poll on making
draft-wang-pce-pcep-extension-native-ip-01 a PCE working group document.
https://datatracker.ietf.org/doc/draft-wang-pce-pcep-extension-native-ip/
Please review the draft and send an email to the list indicating "yes/support"
or "no/do
PCE WG - this version addresses the comments received from the IESG.
Deborah - this version should be good to go to the RFC editor.
Many thanks
Jon
-Original Message-
From: Pce [mailto:pce-boun...@ietf.org] On Behalf Of internet-dra...@ietf.org
Sent: 04 May 2018 10:40
To:
Hi Warren, Ignas,
Sorry for the slow reply. I think Deborah already explained our intent on the
telechat. As this document does not actually define any new path setup types
(just a mechanism to allow multiple path setup types) we can really only make
generalized statements about the sorts of
last call. Authors - please could you ensure that these comments
are addressed promptly. If any changes are required, you can include them in
version -01 of the document.
Many thanks
Jon & Julien
From: Jonathan Hardwick [mailto:jonathan.hardw...@metaswitch.com]
Sent: 10 April 2018 1
Hi Ben
Thanks for the comments - please see [Jon] below.
Best regards
Jon
-Original Message-
From: Pce [mailto:pce-boun...@ietf.org] On Behalf Of Ben Campbell
Sent: 03 April 2018 21:00
To: The IESG
Cc: pce@ietf.org; pce-cha...@ietf.org;
Hi Mirja
Thanks - I agree with you and have corrected the text.
Cheers
Jon
-Original Message-
From: Mirja Kühlewind [mailto:i...@kuehlewind.net]
Sent: 03 April 2018 16:06
To: The IESG
Cc: draft-ietf-pce-lsp-setup-t...@ietf.org; Julien Meuric
;
Hi Martin
Yes, we can assume that implementations will use RSVP-TE if they don't support
this draft.
I think the text you quoted has fallen into the mistake of using normative
language to specify what is already written in RFC 5440. Alvaro picked up
another instance of this. How about we
Hi Spencer
Thanks for your comments. Please see [Jon] below.
Cheers
Jon
-Original Message-
From: Spencer Dawkins [mailto:spencerdawkins.i...@gmail.com]
Sent: 03 April 2018 03:23
To: The IESG
Cc: draft-ietf-pce-lsp-setup-t...@ietf.org; Julien Meuric
Hi Benjamin
Thanks for the comments - please see [Jon] below.
Cheers
Jon
-Original Message-
From: Benjamin Kaduk [mailto:ka...@mit.edu]
Sent: 02 April 2018 19:20
To: The IESG
Cc: draft-ietf-pce-lsp-setup-t...@ietf.org; Julien Meuric
;
Thanks for the comments, Alvaro. Please see [Jon] below.
Cheers
Jon
-Original Message-
From: Alvaro Retana [mailto:aretana.i...@gmail.com]
Sent: 02 April 2018 19:19
To: The IESG
Cc: draft-ietf-pce-lsp-setup-t...@ietf.org; Julien Meuric
;
Dear PCE WG
This is the start of a two week poll on making
draft-barth-pce-association-bidir-04 a PCE working group document.
https://datatracker.ietf.org/doc/draft-barth-pce-association-bidir/
Please review the draft and send an email to the list indicating "yes/support"
or "no/do not
. Authors - please could you ensure that these comments are addressed
promptly. If any changes are required, you can include them in version -01 of
the document.
Many thanks
Jon
From: Jonathan Hardwick [mailto:jonathan.hardw...@metaswitch.com]
Sent: 27 March 2018 12:10
To: pce@ietf.org; draft
This version addresses comments received from the security, OPS and GENART
directorates during IETF last call.
Jon
-Original Message-
From: internet-dra...@ietf.org [mailto:internet-dra...@ietf.org]
Sent: 27 March 2018 13:43
To: Siva Sivabalan <ms...@cisco.com>; Jonathan Ha
Dear PCE WG
This is the start of a two week poll on making
draft-ananthakrishnan-pce-stateful-path-protection-05 a PCE working group
document.
https://datatracker.ietf.org/doc/draft-ananthakrishnan-pce-stateful-path-protection/
Please review the draft and send an email to the list indicating
[mailto:droma...@gmail.com]
Sent: 03 March 2018 10:57
To: Jonathan Hardwick <jonathan.hardw...@metaswitch.com>
Cc: ops-...@ietf.org; pce@ietf.org; i...@ietf.org;
draft-ietf-pce-lsp-setup-type@ietf.org
Subject: Re: Opsdir last call review of draft-ietf-pce-lsp-setup-type-08
On Fri,
This poll has ended, with the result that this document will be adopted by the
PCE working group.
Authors, once the I-D submission tool has reopened, please resubmit the
document as draft-ietf-pce-pcep-flowspec-00.
Best regards
Jon and Julien
From: Jonathan Hardwick [mailto:jonathan.hardw
Hi Roni
Many thanks for the review. You are right, in this case we meant "IETF
Review". I will update the document.
Cheers
Jon
-Original Message-
From: Roni Even [mailto:ron.even@gmail.com]
Sent: 26 February 2018 14:55
To: gen-...@ietf.org
Cc: pce@ietf.org; i...@ietf.org;
Hi Dan
Many thanks for the review. Please see my replies below - look for "Jon>".
Best regards
Jon
-Original Message-
From: Dan Romascanu [mailto:droma...@gmail.com]
Sent: 28 February 2018 15:23
To: ops-...@ietf.org
Cc: pce@ietf.org; i...@ietf.org;
Hi Adrian
Thanks for the suggestion and for the gentle reminder. I have just polled for
adoption of this draft. Given this, it does not sound like you will need this
slot, after all. Of course, if the poll throws up issues that must be
discussed, or something else turns up, please feel free
Dear PCE WG
This is the start of a two week poll on making draft-li-pce-pcep-flowspec-03 a
PCE working group document.
https://datatracker.ietf.org/doc/draft-li-pce-pcep-flowspec/
Please review the draft and send an email to the list indicating "yes/support"
or "no/do not support". If
Adrian
Many thanks for your review. The authors will need to discuss your comments,
and then we'll get back to you.
Best regards
Jon
-Original Message-
From: Pce [mailto:pce-boun...@ietf.org] On Behalf Of Adrian Farrel
Sent: 18 January 2018 22:55
To: 'Julien Meuric'
I am not aware of any IPR that applies to this draft.
Cheers
Jon
-Original Message-
From: Julien Meuric [mailto:julien.meu...@orange.com]
Sent: 15 January 2018 09:41
To: draft-ietf-pce-segment-rout...@ietf.org
Cc: pce@ietf.org
Subject: IPR Check on draft-ietf-pce-segment-routing
Dear
This version addresses Daniele's comments from the routing directorate review.
Best regards
Jon
-Original Message-
From: Pce [mailto:pce-boun...@ietf.org] On Behalf Of internet-dra...@ietf.org
Sent: 16 January 2018 10:52
To: i-d-annou...@ietf.org
Cc: pce@ietf.org
Subject: [Pce] I-D
Hi Daniele
Many thanks for the review. Please see my replies below in … .
Best regards
Jon
From: Daniele Ceccarelli [mailto:daniele.ceccare...@ericsson.com]
Sent: 10 January 2018 10:41
To: (rtg-...@ietf.org)
Cc: rtg-...@ietf.org; pce@ietf.org;
Hi All
This version addresses the comments Julien made in his shepherd's review during
the 2nd WGLC.
Cheers
Jon
-Original Message-
From: Pce [mailto:pce-boun...@ietf.org] On Behalf Of internet-dra...@ietf.org
Sent: 19 December 2017 13:41
To: i-d-annou...@ietf.org
Cc: pce@ietf.org
Hi Julien
Many thanks for the speedy review! Please see a few answers below, marked with
[Jon]. (All other comments are accepted.)
I will hold the document mark-ups until WGLC ends.
Cheers
Jon
-Original Message-
From: Julien Meuric [mailto:julien.meu...@orange.com]
Sent: 21
-routing.
If you think the wording below can be improved for clarity, then please let me
know!
Cheers
Jon
-Original Message-
From: stephane.litkow...@orange.com [mailto:stephane.litkow...@orange.com]
Sent: 20 November 2017 15:32
To: Jonathan Hardwick <jonathan.hardw...@metaswitch.com>
This new revision brings draft-ietf-pce-segment-routing in-line with the new
LSP-SETUP-TYPE-CAPABILITY TLV just published in
draft-ietf-pce-lsp-setup-type-06.
-Original Message-
From: Pce [mailto:pce-boun...@ietf.org] On Behalf Of internet-dra...@ietf.org
Sent: 20 November 2017 15:01
forwards with that?
Best regards
Jon
From: Mahendra Singh Negi [mailto:mahendrasi...@huawei.com]
Sent: 25 July 2017 13:12
To: adr...@olddog.co.uk; 'Julien Meuric' <julien.meu...@orange.com>; Jonathan
Hardwick <jonathan.hardw...@metaswitch.com>; pce@ietf.org; Dhruv Dhod
I'm OK with downgrading the "must" to a "may" (in lowercase).
Cheers
Jon
From: Adrian Farrel [mailto:adr...@olddog.co.uk]
Sent: 19 November 2017 14:43
To: 'Julien Meuric' <julien.meu...@orange.com>; 'Dhruv Dhody'
<dhruv.dh...@huawei.com>; Jonathan Hardwick <j
Hi Stephane
I’m not necessarily saying that this is the way to go, but I would like to
point out the P flag and the I flag in the PCEP common object header. If a
constraint can be relaxed, the PCC sends the relevant object(s) with P=0. If
the PCE decides to relax a constraint, it includes
@nokia.com]
Sent: 17 November 2017 06:47
To: Dhruv Dhody <dhruv.dh...@huawei.com>; Jonathan Hardwick
<jonathan.hardw...@metaswitch.com>; Julien Meuric <julien.meu...@orange.com>;
stephane.litkow...@orange.com
Cc: pce@ietf.org; 'Dhruv Dhody' <dhruv.i...@gmail.com>
Subjec
Hi Julien, see [Jon]s below...
-Original Message-
From: Julien Meuric [mailto:julien.meu...@orange.com]
Sent: 16 November 2017 17:28
To: Jonathan Hardwick <jonathan.hardw...@metaswitch.com>;
stephane.litkow...@orange.com
Cc: pce@ietf.org
Subject: Re: [Pce] Clarifications on PST ha
To: Jonathan Hardwick <jonathan.hardw...@metaswitch.com>; pce@ietf.org
Subject: RE: Clarifications on PST handling in draft-ietf-pce-lsp-setup-type &
draft-ietf-pce-segment-routing
Hi Jon,
Thanks for your feedback.
I see two possibilities here.
1. When the PATH-SETUP-TYPE is not present
tup type
for a PCUpd can be inferred from the current path setup type of the LSP (unless
it is given explicitly), which is a change to draft-ietf-pce-lsp-setup-type.
Does anyone else have an opinion on this?
Thanks
Jon
From: Pce [mailto:pce-boun...@ietf.org] On Behalf Of Jonathan Hardwick
Sen
I think it should be acceptable for the PCUpd not to include the
PATH-SETUP-TYPE, with the implication that there is no change to the path type.
Although I'm not convinced it would be a good idea operationally, I don't think
there's any need to prevent the path type changing on the PCUpd, if an
Jonathan Hardwick has requested publication of
draft-ietf-pce-pcep-exp-codepoints-03 as Proposed Standard on behalf of the PCE
working group.
Please verify the document's state at
https://datatracker.ietf.org/doc/draft-ietf-pce-pcep-exp-codepoints
Hi Dhruv
Thanks for this. Trimming to the open points:
Introduction
The second paragraph is superfluous - I suggest deleting:
Further, in order to support use cases described in [RFC8051],
[I-D.ietf-pce-stateful-pce] specifies a set of extensions to PCEP to
enable stateful control
Hi there
I am the document shepherd for this draft. Please find my review of the draft
below.
Many thanks for writing this draft. It looks in good shape overall. There are
just a few clarifications I would like to make before we forward it to the IESG
for publication.
Cheers
Jon
Abstract
Re-sending to the correct DL :)
From: Jonathan Hardwick
Sent: 12 November 2017 12:02
To: 'draft-ietf-pce-exp-codepoi...@ietf.org'
<draft-ietf-pce-exp-codepoi...@ietf.org>
Cc: 'pce@ietf.org' <pce@ietf.org>; pce-cha...@ietf.org
Subject: Shepherd's review of draft-ietf-pce-exp-co
Dear PCE working group
This email starts a working group last call for
draft-ietf-pce-pcep-exp-codepoints-02.
https://datatracker.ietf.org/doc/draft-ietf-pce-pcep-exp-codepoints/
Please read the document and reply to the PCE mailing list whether you believe
this document is ready to be
This version addresses the feedback we received from the IESG. If anyone has
any concerns with the changes, please shout ASAP.
Best regards
Jon
-Original Message-
From: Pce [mailto:pce-boun...@ietf.org] On Behalf Of internet-dra...@ietf.org
Sent: 09 October 2017 08:27
To:
Hi Alvaro
Many thanks for your comments. I'm picking up this thread and replying as PCE
working group chair, as the authors are unavailable. I am very sorry for the
delay.
For some reason I can't find the original email with your comments in, so I
have scraped the text from the
Hi Eric
Many thanks for these comments. I'm picking up this thread and replying as PCE
working group chair, as the authors are unavailable. I am very sorry for the
delay.
Please see my proposed resolutions inline below, marked with "Jon>"
Best regards
Jon
Hi Adam
Many thanks for these comments. I'm picking up this thread and replying as PCE
working group chair, as the authors are unavailable. I am very sorry for the
delay.
Please see my proposed resolutions inline below, marked with "Jon>"
Best regards
Jon
Hi Spencer
Many thanks for these comments. I'm picking up this thread and replying as PCE
working group chair, as the authors are unavailable. I am very sorry for the
delay.
Please see my proposed resolutions inline below, marked with "Jon>"
Best regards
Jon
Dear PCE WG
We have received a request from the authors of draft-ietf-pce-association-group
for an early code point allocation.
The process for early code point allocation is described in RFC 7120. The
draft is required to meet several criteria, including:
b. The format, semantics,
com>; Jonathan Hardwick
<jonathan.hardw...@metaswitch.com>; Deborah A Brungard <db3...@att.com>; Adrian
Farrel <adr...@olddog.co.uk>; d.k...@lancaster.ac.uk; Dhruv Dhody
<dhruv.dh...@huawei.com>
Subject: Best Wishes for the future of PCE WG !
Dear WG,
Almost 12 yea
not as ugly as RSVP-TE-NON-SUPPORT.
Cheers
Jon
From: Adrian Farrel [mailto:adr...@olddog.co.uk]
Sent: 21 July 2017 19:55
To: Jonathan Hardwick <jonathan.hardw...@metaswitch.com>; pce@ietf.org;
draft-ietf-pce-lsp-setup-t...@ietf.org; draft-ietf-pce-segment-rout...@ietf.org
Cc: pce-cha...@ie
Dear PCE-ers
I don't want to distract from the SDN topic too much, but we have an important
decision to make about draft-ietf-pce-lsp-setup-type.
The shepherd review raised an issue that there is no way for a PCEP speaker to
indicate that it can't (or won't) support RSVP-TE as a path setup
Dear PCE WG
The purpose of this email is to initiate a discussion about whether we want to
extend PCEP to allow it to replace the functions that are traditionally
provided by the routing and signalling protocols.
Originally, PCEP was designed with the goal of providing a distributed path
This poll for adoption has concluded, with the result that the document will be
adopted by the PCE working group.
Authors, please resubmit this version of the draft with the new name
draft-ietf-pce-stateful-pce-lsp-scheduling-00.
Thanks
Jon
From: Jonathan Hardwick [mailto:jonathan.hardw
This email is to announce that Dan King is standing down as secretary to the
PCE working group. The chairs would like to place on record our thanks and
heartfelt gratitude to Dan for all of the work he did in this role. We look
forward to Dan's involvement with PCE continuing long into the
All,
This is the start of a two week poll on making
draft-zhuang-pce-stateful-pce-lsp-scheduling-05 a PCE working group document.
https://datatracker.ietf.org/doc/draft-zhuang-pce-stateful-pce-lsp-scheduling/
Please review the draft and send an email to the list indicating "yes/support"
or
This poll for adoption has concluded, with the result that the document will be
adopted by the PCE working group.
Authors, please resubmit this version of the draft with the new name
draft-ietf-pce-stateful-hpce-00.
Thanks
Jon
From: Jonathan Hardwick
Sent: 01 June 2017 13:25
To: pce@ietf.org
Cc
All,
This is the start of a two week poll on making
draft-dhodylee-pce-stateful-hpce-03 a PCE working group document.
https://datatracker.ietf.org/doc/draft-dhodylee-pce-stateful-hpce/
Please review the draft and send an email to the list indicating "yes/support"
or "no/do not support". If
Apologies for the delay. This poll has ended with the result that the document
will be adopted by the working group.
Authors, please resubmit this version of the draft as
draft-ietf-pce-applicability-actn-00.
Thanks
Jon
From: Jonathan Hardwick [mailto:jonathan.hardw...@metaswitch.com]
Sent: 25
This new version of the stateful PCE draft resolves the comments received
during IETF last call.
Thanks for your patience!
Best regards
Jon
-Original Message-
From: Pce [mailto:pce-boun...@ietf.org] On Behalf Of internet-dra...@ietf.org
Sent: 17 May 2017 15:47
To: i-d-annou...@ietf.org
Hi all
Thanks for your feedback on this issue. I think we are probably in a position
to close this issue down. To summarize:
- The original intent was that the PCE MUST close the session.
- It seems that nobody has implemented the "exiting resource limit exceeded
state" notification.
On the
Hi PCE WG
I've been tidying up the stateful PCE draft to prepare it for publication and I
have discovered an inconsistency in how the stateful PCE is supposed to handle
an overflow of its per-PCC resource limit. In section 5.6 it says:
A PCE implementing a limit on the resources a single
All,
This is the start of a two week poll on making
draft-dhody-pce-applicability-actn-02 a PCE working group document.
https://datatracker.ietf.org/doc/draft-dhody-pce-applicability-actn/
Please review the draft and send an email to the list indicating "yes/support"
or "no/do not support".
make this clearer.
Cheers
Jon
-Original Message-
From: Julien Meuric [mailto:julien.meu...@orange.com]
Sent: 11 April 2017 16:00
To: Jonathan Hardwick <jonathan.hardw...@metaswitch.com>; Lionel Morand
<lionel.mor...@orange.com>; ops-...@ietf.org
Cc: draft-ietf-pce-
Hi Lionel
Many thanks for a very thorough review. I'm picking up this thread and
replying as PCE working group chair, as the authors are unavailable. I
apologise for the delay.
Please see my proposed resolutions inline below, marked with "Jon>"
Best regards
Jon
-Original Message-
Hi Mirja
Many thanks for your comment. I'm picking up this thread and replying as PCE
working group chair, as the authors are unavailable. I apologise for the delay.
It is possible for a PCC or a stateful PCE not to support updates and still to
advertise the STATEFUL-PCE-CAPABILITY TLV.
1 - 100 of 173 matches
Mail list logo