Re: [pcp] FW: Consensus from the WG meeting today

> -----Original Message-----
> From: pcp-bounces@ietf.org [mailto:pcp-bounces@ietf.org] On Behalf Of
> Reinaldo Penno (repenno)
> Sent: Friday, November 09, 2012 6:13 AM
> To: pcp@ietf.org
> Subject: [pcp] FW: Consensus from the WG meeting today
> 
> 
> 
> On 11/8/12 6:09 PM, "Dave Thaler" <dthaler@microsoft.com> wrote:
> 
> >The following three items had strong consensus (loud hums for, silence
> >against)
> >during the meeting today:
> >
> >1) Add text in pcp-base recommending that when the PCP server receives
> >a PEER, it should give the flow a longer timeout than when PCP isn't
> >used.
> >(Several other
> >documents, including requirements documents, have text that depends on
> >this fact but it's not stated anywhere.)

There was no email discussing this proposal, so I guess folks agree.  Text
will be:

  "So that PCP clients can reduce the frequency of their NAT and	
   firewall keepalive messages, it is RECOMMENDED that lifetimes of	
   mappings created or lengthened with PEER be longer than the lifetimes

   of implictly-created mappings."

-d

> >2) Adopt draft-boucadair-pcp-server-selection as a WG item.  The actual
> >content was recently separated out of draft-ietf-pcp-dhcp which was
> >already a WG doc.
> >(This is considered to be part of the existing milestone items, the WG
> >just decided to split a milestone item into multiple docs.)
> >
> >3) Adopt draft-boucadair-pcp-nat64-prefix64-option as a WG item.   This
> >is not
> >currently a milestone item.   The chairs will confirm with the AD what
> >needs to
> >happen.
> >
> >If anyone on the list has a strong objection, let us know, as we plan
> >to move forward with the above.
> >
> >Thanks for everyone's participation in these discussions at the meeting
> >today.
> >
> >-Dave
> >
> >
> >
> 
> _______________________________________________
> pcp mailing list
> pcp@ietf.org
> https://www.ietf.org/mailman/listinfo/pcp