Re: [nat66] Comments on draft-mrw-nat66-12

[Fred Baker <[e-mail]>]

On Mar 15, 2011, at 4:12 PM, james woodyatt wrote:

> On Mar 15, 2011, at 15:51 , Fred Baker wrote:
>> 
>> To my mind, section 5 spends quite a bit of effort indicating that there are issues around differences in addresses.
> 
> It does, but I think there might be room to improve section 2.4 further by discussing the problem of choosing the correct valid and preferred lifetimes for routers advertising the internal network prefix.  There may also be ramifications for firewalls that implement I-D.ietf-pcp-base.

In RIPng, IS-IS, OSPFv3, and BGP-4+, route lifetimes are not a question of attributes of the prefix such as whether it is internal or external. They are attributes specified in the routing protocol. In any variant of RIP, the system originating the prefix does so if and only if the relevant interface is up, and does so as often as the announcement timer fires - by default, in RIPng, every 30 seconds. In OSPF, a prefix LSA similarly reflects the prefix's state as seen by its originator, is refreshed every 1800 seconds as long as the prefix remains up, and is withdrawn should it go down. IS-IS follows suit, and so does BGP4+. 


To my mind, the ramifications for the port control protocol are very simple. 

AN NPTv6 TRANSLATOR DOES NOT, EVER, UNDER ANY CIRCUMSTANCES, SCREW WITH PORTS. COLD STOP, NOTHING MORE TO SAY, AND THE DRAFT SPENDS A FAIR BIT OF SPACE SAYING THAT INCLUDING THE WORDS "MUST NOT".

If a firewall, such as specified in RFC 6092, is opening or closing port filters, that is something the filter logic and its manager do. The firewall might be configured to open these ports, close those ports, and close a third set of ports unless someone asks for them to be opened. The PCP conversation is with the firewall functionality, which is COMPLETELY AND 100% SEPARATE FROM THE NPTv6 TRANSLATOR FUNCTIONALITY.

Hence, I have no clue what you're getting at in asking me to wax eloquent on in either topic, and mystified as to why you would want me to. It's irrelevant to NPTv6.