Alright, I'm going to bow out of the discussion as it's clear that the 
bickering going on here is mostly tangential to discussion of the specific 
proposal that the authors have put forward...and is probably not helping them 
accomplish what they intended to accomplish. For any part I played in helping 
the discussion stray off track, I apologize, Fred and Margaret. My initial 
response was simply to illustrate that the particular proposal still would not 
meet my organizations particular usage case and try to provide some detail of 
what that usage case entailed. That's perfectly fine, not every proposal needs 
to be applicable to every usage case.
Beyond that, I got drawn into defending the rationale behind the particular 
usage case I described and, by extension, my professional competency for 
holding that rationale. Probably a discussion I should not have allowed myself 
to be baited into.

I'll be happy to answer any particulars about the usage case I am looking to 
see filled or my rationale behind that usage case, off-list..... so as not to 
clutter up this list with topics not relevant to it.

The one, on list suggestion, I might offer would be to consider amending the 
title of the draft to clarify that it is a bit of different animal from NAT44 
simply transplanted into IPv6
and/or perhaps include a statement in the introduction that the draft is not 
intended to address the other PERCEIVED benefits of NAT44 (simple security, 
network abstraction, etc). Some may question whether said perception of 
benefits is accurate or not but I don't think it's arguable that the PERCEPTION 
at least is fairly wide spread. That way, individuals who WERE looking for 
those perceived benefits would know, right up front, that they were looking in 
the wrong place for them. The word "stateless" should generally imply to the 
reader that such other functionality isn't included in this draft, but I think 
it's better to be explicit when conveying such information rather then relying 
on the reader to draw implicit conclusions.



Christopher Engel
Network Infrastructure Manager
SponsorDirect
[email protected]
www.SponsorDirect.com
p(914) 729-7218
f (914) 729-7201

_______________________________________________
nat66 mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/nat66

Reply via email to