2012/9/7 GangChen <phdg...@gmail.com>

> Hello Woj and all,
>
> Before you submit the MAP-T, I have a question whether we need it
> given MAP-E is staying on standard track.
> If I understood correctly, the motivation doing MAP-T is mainly driven
> by ACL requirements. I don't see there are any needs from an operator
> side on this point. Therefore, I don't see any needs publishing MAP-T
> as a WG draft.
>

unfortunately, however, your understanding, IMHO, is not fairly correct. on
the other hand, my company has had a very concrete use-case where MAP-T is
needed. - maoke


> In order to not disturb the thread, I would create a new thread to discuss
> that.
>
> BRs
>
> Gang
>
>
> 2012/9/6, Wojciech Dec <wdec.i...@gmail.com>:
> > With the standalone MAP-T draft coming shortly...
> >
> > On 5 September 2012 10:31, Ole Trøan <otr...@employees.org> wrote:
> >
> >> to avoid any confusion.
> >> the '-' below indicates subtraction.
> >>
> >> cheers,
> >> Ole
> >>
> >>
> >> On Sep 5, 2012, at 10:16 , Ole Trøan wrote:
> >>
> >> > hello,
> >> >
> >> > here is an update of the MAP document resulting from the changed
> >> direction from Vancouver.
> >> >
> >> > this _should_ be "draft-ietf-softwire-map-01 - MAP-T".
> >> >
> >> > cheers,
> >> > Ole
> >> >
> >> >>
> >> >> 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
> >> >>      Filename        : draft-ietf-softwire-map-02.txt
> >> >>      Pages           : 29
> >> >>      Date            : 2012-09-05
> >> >>
> >> >> Abstract:
> >> >>  This document describes a mechanism for transporting IPv4 packets
> >> >>  across an IPv6 network, 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-02
> >> >>
> >> >> A diff from the previous version is available at:
> >> >> http://www.ietf.org/rfcdiff?url2=draft-ietf-softwire-map-02
> >> >>
> >> >>
> >> >> Internet-Drafts are also available by anonymous FTP at:
> >> >> ftp://ftp.ietf.org/internet-drafts/
> >> >>
> >> >> _______________________________________________
> >> >> Softwires mailing list
> >> >> Softwires@ietf.org
> >> >> https://www.ietf.org/mailman/listinfo/softwires
> >> >
> >>
> >>
> >> _______________________________________________
> >> Softwires mailing list
> >> Softwires@ietf.org
> >> https://www.ietf.org/mailman/listinfo/softwires
> >>
> >>
> >
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires
>
_______________________________________________
Softwires mailing list
Softwires@ietf.org
https://www.ietf.org/mailman/listinfo/softwires

Reply via email to