Re: [BEHAVE] Multicast IPv4-embedded Address Format

> -----Original Message-----
> From: Behcet Sarikaya [mailto:behcetsarikaya@yahoo.com]
> Sent: Wednesday, January 26, 2011 7:48 AM
> To: Dan Wing; Xing Li
> Cc: congxiao; behave@ietf.org
> Subject: Re: [BEHAVE] Multicast IPv4-embedded Address Format
> 
> Hi Dan,
> 
> I realize that it is probably late to do something on this document.
> 
> But I hope you agree with me on what I said below :-)

We can correct / augment the information with follow-on documents,
including -- if we find it necessary -- doing an "Update:" of 
draft-ietf-behave-v6v4-xlate.

-d

> --b
> 
> 
> 
> 
> > >
> > >
> > > >  The stateless translation document is
> > > >https://datatracker.ietf.org/doc/draft-ietf-behave-v6v4-
> > >  xlate/?include_text=1,
> > > >
> > > >
> > > >which clearly  mentions the applicability and limitations of
> > > IPv4/IPv6
> > > >  translation for the multicast packets.
> > >
> > > Hi Xing,
> > >
> > >   I did not know this. Now I checked, you are right.
> > >
> > > However the stateless translation document does not really state
> much
> > > about
> > > multicast.
> > > I still believe that any multicast  related text in the current
> unicast
> > > NAT64
> > > documents should be  removed, including some sporadic text in
> > >  draft-ietf-behave-v6v4-xlate-23.
> > >
> > > I am not sure if they have  been reviewed.
> >
> > draft-ietf-behave-v6v4-xlate has been in the RFC Editor's  queue
> > since October, 2010, because it had completed BEHAVE working group
> > last call, IETF last call, and IESG review.  Dates are here:
> >
> > https://datatracker.ietf.org/doc/draft-ietf-behave-v6v4-
> xlate/history/
> >
> > -d
> >
> >
> > _______________________________________________
> > Behave  mailing list
> > Behave@ietf.org
> > https://www.ietf.org/mailman/listinfo/behave
> >
> 
> 
> 