I've read it and support adoption as well. I also agree with JF's point that the NAT doesn't do logging and inspection. While that is an important consideration deployment, I think section 2.4.1 should explicitly state that such logging and inspection are done on another system, not the NAT64 one.
Regards On Tue, May 5, 2015 at 4:11 PM, JF Tremblay < [email protected]> wrote: > > > On May 5, 2015, at 3:11 AM, Huangjing (A) <[email protected]> > wrote: > > > >>> > >>> Good to know more if you point me a reference of "port block > >> randomization”. > >> > >> There isn’t a reference. I might have coined the term a couple of years > back, > >> not sure. This is basically the act of randomizing the assignments of > blocks > >> instead or in conjunction with port randomization within the block. > >> This could be a concept defined and discussed in this document. > > > > I think you are talking about the port block randomization algorithms > similar to those defined in RFC6431. > > Will add some analysis and reference > > Thanks for the reference, James. Interesting. I had in mind a > non-cryptographically random set of port, which doesn’t seem to be handled > in RFC6431. That would basically be a continuous set of ports where the > first port is assigned randomly or semi-randomly (could be on block > boundary for example). This concept could be defined and discussed in this > document, but it’s just a minor point for discussion/improvement. > > JF > > > > _______________________________________________ > sunset4 mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/sunset4 > -- Mukom Akong T. http://about.me/perfexcellence | twitter: @perfexcellent ------------------------------------------------------------------------------------------------------------------------------------------ “When you work, you are the FLUTE through whose lungs the whispering of the hours turns to MUSIC" - Kahlil Gibran -------------------------------------------------------------------------------------------------------------------------------------------
_______________________________________________ sunset4 mailing list [email protected] https://www.ietf.org/mailman/listinfo/sunset4
