Re: [v6ops] reclassify 464XLAT as standard instead of info

[JORDI PALET MARTINEZ <[e-mail]>]

Hi Lee,

See below in-line.

Regards,
Jordi
 

-----Mensaje original-----
De: v6ops <[e-mail]> en nombre de Lee Howard <[e-mail]>
Responder a: <[e-mail]>
Fecha: viernes, 22 de septiembre de 2017, 14:56
Para: Lee Howard <[e-mail]>
CC: "[e-mail] WG" <[e-mail]>
Asunto: Re: [v6ops] reclassify 464XLAT as standard instead of info

    As to the original question, I have a couple of questions:
    
    1. What is gained by promoting rfc6877 "464XLAT: Combination of Stateful
    and Stateless Translation”?  Regardless of whether the correct promotion
    path is BCP or Proposed Standard, what is the goal?

[Jordi] My point is: I understand that when 464XLAT was proposed, it was not considered at the same level as other transition mechanisms, which are, from the start, standards track. Now that this is the most successful (in terms of number of users vs. all the other transition mechanisms), in my opinion there is no reason to discriminate it. So, either we drop to informational all the transition mechanisms that have so much lower degree of success or even to historic or deprecated those that are not used. Is a matter of fairness and recognize the reality.
    
    2. rfc2026 “The Internet Standards Process”  says a BCP is the "best
    current thinking on a statement of principle or on what is believed to be
    the best way to perform some operations.”  What principle or what
    operations is 464xlat best for?
    
[Jordi] Well, I was suggesting standards track, not BCP. So not sure how to read this question myself. Actually, I’ve drafted already (started two months ago, and not related at all to this discussion, but for lack of time availability, haven’t completed it yet, hopefully can have it early next week) a BCP which initially I’ve titled “464XLAT Deployment Guidelines in Operator Networks”. The idea come out after we had the discussion of deploying at the IETF network 464XLAT instead of just NAT64. In this document I’m describing how, according to my experience (and hopefully inputs from others once a first version is published), 464XLAT is being deployed in both cellular and non-cellular networks.
   
    The chairs are working out how to handle this request, and answers to
    these questions will help us.
    
    Thanks,
    
    Lee
    
    
    
    _______________________________________________
    v6ops mailing list
    [e-mail]
    https://www.ietf.org/mailman/listinfo/v6ops
    



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.