Re: [Pce] I-D Action: draft-ietf-pce-pceps-18.txt

Hi WG, 

An update is made after discuss with Eric. Thanks Eric for continuing the discussion on your 'discuss'. 

The change made is in the case of TLS negotiation failure after both PCEP peers have sent the StartTLS message. 

OLD: 
   After the exchange of StartTLS messages, if the TLS negotiation fails
   for some reason (e.g. the required mechanisms for certificate
   revocation checking are not available), both peers SHOULD immediately
   close the connection.  Since the initiator has no way to know if the
   peer is willing to accept PCEP connection without TLS, based on the
   local policy, it MAY attempt to re-establish the PCEP session without
   TLS.  The attempt to re-establish the PCEP session without TLS SHOULD
   be limited to only once.
NEW:  
   After the exchange of StartTLS messages, if the TLS negotiation fails
   for some reason (e.g. the required mechanisms for certificate
   revocation checking are not available), both peers MUST immediately
   close the connection.
END

See diff at - https://www.ietf.org/rfcdiff?url1=draft-ietf-pce-pceps-16&url2=draft-ietf-pce-pceps-18

With this update all comments during IESG evaluation are handled. 

Thanks! 
Dhruv

> -----Original Message-----
> From: Pce [mailto:pce-bounces@ietf.org] On Behalf Of internet-
> drafts@ietf.org
> Sent: 05 September 2017 08:47
> To: i-d-announce@ietf.org
> Cc: pce@ietf.org
> Subject: [Pce] I-D Action: draft-ietf-pce-pceps-18.txt
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Path Computation Element WG 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-18.txt
> 	Pages           : 25
> 	Date            : 2017-09-04
> 
> 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 describes 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 the
>    flexibility and extensibility of PCEP.
> 
>    This document updates RFC 5440 in regards to the PCEP initialization
>    phase procedures.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-pce-pceps/
> 
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-pce-pceps-18
> https://datatracker.ietf.org/doc/html/draft-ietf-pce-pceps-18
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-pce-pceps-18
> 
> 
> 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/
> 
> _______________________________________________
> Pce mailing list
> Pce@ietf.org
> https://www.ietf.org/mailman/listinfo/pce