-Message d'origine-
De : Tom Taylor [mailto:tom.taylor.s...@gmail.com]
Envoyé : mercredi 13 juin 2012 17:44
À : BOUCADAIR Mohamed OLNC/NAD/TIP
Cc : liu dapeng; softwires@ietf.org
Objet : Re: [Softwires] I-D Action:
draft-ietf-softwire-stateless-4v6-motivation-02.txt
I think what
dapeng; softwires@ietf.org
Objet : Re: [Softwires] I-D Action:
draft-ietf-softwire-stateless-4v6-motivation-02.txt
I think what Dapeng wants to convey would be achieved if you
changed the
may to will typically:
... state will typically exist in the customer premises side
Is this acceptable
Taylor [mailto:tom.taylor.s...@gmail.com]
Envoyé : mercredi 13 juin 2012 17:44
À : BOUCADAIR Mohamed OLNC/NAD/TIP
Cc : liu dapeng; softwires@ietf.org
Objet : Re: [Softwires] I-D Action:
draft-ietf-softwire-stateless-4v6-motivation-02.txt
I think what Dapeng wants to convey would be achieved if you
@ietf.org
Objet : Re: [Softwires] I-D Action:
draft-ietf-softwire-stateless-4v6-motivation-02.txt
As a reader of the document, not co-author any related document, I
believe people who is not involved the whole process
(e.g. edit the
documents, design the solutions,etc) couldn't understand
2012 17:44
À : BOUCADAIR Mohamed OLNC/NAD/TIP
Cc : liu dapeng; softwires@ietf.org
Objet : Re: [Softwires] I-D Action:
draft-ietf-softwire-stateless-4v6-motivation-02.txt
I think what Dapeng wants to convey would be achieved if you
changed the
may to will typically:
... state will typically
Re-,
Please see inline.
Cheers,
Med
-Message d'origine-
De : liu dapeng [mailto:maxpass...@gmail.com]
Envoyé : mercredi 13 juin 2012 12:09
À : BOUCADAIR Mohamed OLNC/NAD/TIP
Cc : softwires@ietf.org
Objet : Re: [Softwires] I-D Action:
draft-ietf-softwire-stateless-4v6-motivation-02
...@orange.com wrote:
Re-,
Please see inline.
Cheers,
Med
-Message d'origine-
De : liu dapeng [mailto:maxpass...@gmail.com]
Envoyé : mercredi 13 juin 2012 12:09
À : BOUCADAIR Mohamed OLNC/NAD/TIP
Cc : softwires@ietf.org
Objet : Re: [Softwires] I-D Action:
draft-ietf-softwire-stateless-4v6-motivation
I prefer Tom suggestion. It is typical to have a NAT but not a must or
should.
On 6/13/12 12:38 PM, liu dapeng maxpass...@gmail.com wrote:
I can change may to should to
please you but it really does make sense.
= thanks
smime.p7s
Description: S/MIME cryptographic signature
: BOUCADAIR Mohamed OLNC/NAD/TIP
Cc : liu dapeng; softwires@ietf.org
Objet : Re: [Softwires] I-D Action:
draft-ietf-softwire-stateless-4v6-motivation-02.txt
I think what Dapeng wants to convey would be achieved if you
changed the
may to will typically:
... state will typically exist in the customer
-annou...@ietf.org
Cc : softwires@ietf.org
Objet : [Softwires] I-D Action:
draft-ietf-softwire-stateless-4v6-motivation-02.txt
A New Internet-Draft is available from the on-line
Internet-Drafts directories.
This draft is a work item of the Softwires Working Group of the IETF.
Title
2012/6/12, Ole Trøan otr...@employees.org:
Ok, then we can make this more clear in our document.
States still should be maintained in other equipments, e.g. customer
premises equipment or host, in order to restrict IP address or port
number
information into the configured context except that
Re-,
Please see inline.
Cheers,
Med
-Message d'origine-
De : liu dapeng [mailto:maxpass...@gmail.com]
Envoyé : mardi 12 juin 2012 11:49
À : BOUCADAIR Mohamed OLNC/NAD/TIP
Cc : softwires@ietf.org
Objet : Re: [Softwires] I-D Action:
draft-ietf-softwire-stateless-4v6-motivation-02.txt
As a reader of the document, not co-author any related document, I
believe people who is not involved the whole process (e.g. edit the
documents, design the solutions,etc) couldn't understand the story
behind that. I personally have sincerely heard some people presenting
and evaluating this
A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Softwires Working Group of the IETF.
Title : Motivations for Carrier-side Stateless IPv4 over IPv6
Migration Solutions
Author(s) : Mohamed Boucadair
14 matches
Mail list logo
