Re: [pcp] I-D Action: draft-ietf-pcp-third-party-id-option-02.txt

Dear PCP-Chairs,

any news on this? All comments have been addressed in February. Given that we approach May, an update from your side would be highly appreciated!

Best,

Rolf 

NEC Europe Ltd | Registered Office: Athene, Odyssey Business Park, West End  Road, London, HA4 6QE, GB | Registered in England 2832014

> -----Original Message-----
> From: pcp [mailto:pcp-bounces@ietf.org] On Behalf Of Andreas Ripke
> Sent: Montag, 9. Februar 2015 16:50
> To: pcp@ietf.org
> Subject: Re: [pcp] I-D Action: draft-ietf-pcp-third-party-id-option-
> 02.txt
> 
> Dear all,
> 
> This new version addresses Med's comments.
> The lifetimes of the error result codes are added in section 4.1.
> RFC6887 is cited and wording is changed in section 7.
> 
> We have responded to all matters raised during the WGLC.
> 
> Thanks again for reviewing.
> 
> Andreas
> 
> > -----Original Message-----
> > From: pcp [mailto:pcp-bounces@ietf.org] On Behalf Of
> > internet-drafts@ietf.org
> > Sent: Monday, February 09, 2015 4:15 PM
> > To: i-d-announce@ietf.org
> > Cc: pcp@ietf.org
> > Subject: [pcp] I-D Action: draft-ietf-pcp-third-party-id-option-
> 02.txt
> >
> >
> > A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> >  This draft is a work item of the Port Control Protocol Working Group
> > of the IETF.
> >
> >         Title           : PCP Third Party ID Option
> >         Authors         : Andreas Ripke
> >                           Rolf Winter
> >                           Thomas Dietz
> >                           Juergen Quittek
> >                           Rafael Lopez da Silva
> > 	Filename        : draft-ietf-pcp-third-party-id-option-02.txt
> > 	Pages           : 12
> > 	Date            : 2015-02-09
> >
> > Abstract:
> >    This document describes a new Port Control Protocol (PCP) option
> >    called THIRD_PARTY_ID.  It is designed to be used in combination
> with
> >    the THIRD_PARTY option specified in RFC 6887 but can also be used
> >    without it.  The THIRD_PARTY_ID serves to identify a Third Party
> in
> >    situations where a third party's IP address contained in the
> >    THIRD_PARTY option does not provide sufficient information to
> create
> >    requested mappings in a PCP-controlled device.
> >
> >
> > The IETF datatracker status page for this draft is:
> > https://datatracker.ietf.org/doc/draft-ietf-pcp-third-party-id-
> option/
> >
> > There's also a htmlized version available at:
> > http://tools.ietf.org/html/draft-ietf-pcp-third-party-id-option-02
> >
> > A diff from the previous version is available at:
> > http://www.ietf.org/rfcdiff?url2=draft-ietf-pcp-third-party-id-
> option-
> > 02
> >
> >
> > 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/
> >
> > _______________________________________________
> > pcp mailing list
> > pcp@ietf.org
> > https://www.ietf.org/mailman/listinfo/pcp
> 
> _______________________________________________
> pcp mailing list
> pcp@ietf.org
> https://www.ietf.org/mailman/listinfo/pcp