hi Med and others,

IMHO, MAP doesn't depend on any specific provisioning methodology and even
manual configuration works well. on the other hand, unified CPE should
define a certain method that suitable for both MAP and lw4o6. This
difference/relationship doesn't support the bi-directional mutual citation.

- maoke



2013/8/13 <[email protected]>

> Hi Satoru,****
>
> ** **
>
> Provisioning-related discussion should be included in the unified CPE not
> in each individual document. This is true for MAP, lw4o6, etc. ****
>
> Ensuring a coherency among ongoing specification documents will require a
> coordination effort among existing documents.  ****
>
> ** **
>
> Cheers,****
>
> Med****
>
> ** **
>
> *De :* Satoru Matsushima [mailto:[email protected]]
> *Envoyé :* mardi 13 août 2013 08:05
> *À :* BOUCADAIR Mohamed OLNC/OLN
> *Cc :* [email protected]
> *Objet :* Re: [Softwires] I-D Action: draft-ietf-softwire-map-08.txt****
>
> ** **
>
> Hi Med, thank you for your comments.****
>
> ** **
>
> When I did review the current version of unified cpe draft, I couldn't
> find any kind of stuff on which the map draft should depend so please point
> things out more specific to what unified cpe draft want map to be.****
>
> ** **
>
> cheers,****
>
> --satoru****
>
> ** **
>
> On Mon, Aug 12, 2013 at 10:53 PM, <[email protected]> wrote:***
> *
>
> Ole, all,
>
> I have two comments about the new version:
>
> * The document does not cite the unified CPE I-D. I think Senthil already
> raised this point to the authors, but it seems this was not taken into
> account. I suggest adding that document as a normative reference.
>
> * I-D.ietf-softwire-map-dhcp is to be listed as an example to achieve
> provisioning (other means can be supported). This ref can be cited as
> informative and not normative one.
>
> Cheers,
> Med
>
> >-----Message d'origine-----
> >De : [email protected] [mailto:[email protected]]
> >De la part de [email protected]
> >Envoyé : lundi 12 août 2013 14:17
> >À : [email protected]
> >Cc : [email protected]
> >Objet : I-D Action: draft-ietf-softwire-map-08.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           : Mapping of Address and Port with Encapsulation
> >(MAP)
> >       Author(s)       : Ole Troan
> >                          Wojciech Dec
> >                          Xing Li
> >                          Congxiao Bao
> >                          Satoru Matsushima
> >                          Tetsuya Murakami
> >                          Tom Taylor
> >       Filename        : draft-ietf-softwire-map-08.txt
> >       Pages           : 30
> >       Date            : 2013-08-12
> >
> >Abstract:
> >   This document describes a mechanism for transporting IPv4 packets
> >   across an IPv6 network using IP encapsulation, and a generic
> >   mechanism for mapping between IPv6 addresses and IPv4 addresses and
> >   transport layer ports.
> >
> >
> >The IETF datatracker status page for this draft is:
> >https://datatracker.ietf.org/doc/draft-ietf-softwire-map
> >
> >There's also a htmlized version available at:
> >http://tools.ietf.org/html/draft-ietf-softwire-map-08
> >
> >A diff from the previous version is available at:
> >http://www.ietf.org/rfcdiff?url2=draft-ietf-softwire-map-08
> >
> >
> >Please note that it may take a couple of minutes from the time of
> >submission
> >until the htmlized version and diff are available at tools.ietf.org.
> >
> >Internet-Drafts are also available by anonymous FTP at:
> >ftp://ftp.ietf.org/internet-drafts/
> >
> >_______________________________________________****
>
> >I-D-Announce mailing list
> >[email protected]
> >https://www.ietf.org/mailman/listinfo/i-d-announce
> >Internet-Draft directories: http://www.ietf.org/shadow.html
> >or ftp://ftp.ietf.org/ietf/1shadow-sites.txt****
>
> _______________________________________________
> Softwires mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/softwires****
>
> ** **
>
> _______________________________________________
> Softwires mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/softwires
>
>
_______________________________________________
Softwires mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/softwires

Reply via email to