Re: [pcp] secdir review of draft-ietf-behave-lsn-requirements

2012-07-11 Thread Sam Hartman
> "Simon" == Simon Perreault writes: Simon> MUST NOT permit the lifetime of a mapping to be reduced beyond its Simon> current life or be set to zero (deleted) OK. >> and MUST NOT support the third-party option. Simon> I think pcp-base-26 added restrictions to THIRD_PARTY

Re: [pcp] secdir review of draft-ietf-behave-lsn-requirements

2012-07-10 Thread Shin Miyakawa
>> Then that still permits the case of third_party for administration >> motivating the text in 13.1. > > Makes sense to me. +1 > How about adding a sentence like... > > "CGN as described in this document does not provide any security > benefits over either single-user NAT or no NAT at all." I

Re: [pcp] secdir review of draft-ietf-behave-lsn-requirements

2012-07-10 Thread Simon Perreault
On 07/10/2012 04:03 PM, Sam Hartman wrote: >> and MUST NOT support the third-party option. Simon> I think pcp-base-26 added restrictions to THIRD_PARTY so that it could Simon> be used in CGN scenarios. If that is right, wouldn't it then make Simon> sense to allow THIRD_PARTY