Re: Re: [nemo] NEMO Basic Support: About terminology

"James Kempf" <[email protected]>
Newsgroups gmane.ietf.seamoby
Message-ID <025a01c3602b$26e46b70$9f6015ac@dclkempt40>
The draft is currently with the IESG, recommended to be published as
Informational. According to Draft Tracker, the state is AD Evaluation.

            jak

----- Original Message ----- 
From: "Vijay Devarapalli" <[email protected]>
To: "Thierry Ernst" <[email protected]>
Cc: "nemo" <[email protected]>; <[email protected]>
Sent: Monday, August 11, 2003 9:59 AM
Subject: [Seamoby] Re: [nemo] NEMO Basic Support: About terminology


> I have cc'ed Seamoby list.
>
> Thierry Ernst wrote:
> >
> > Dear all,
> >
> > draft-ietf-nemo-basic-support-pre01.txt
> >
> > Mobile Network Prefix
> >
> >               The IPv6 prefix advertised in the Mobile Network
> >               by one or more Mobile Routers.  There could be multiple
> >               prefixes in the Mobile Network.
> >
> > This is already defined in the terminology drafts (seamoby and NEMO):
> >
> >   draft-ietf-seamoby-mobility-terminology-04.txt
> >
> >      Mobile Network Prefix
> >
> >        A bit string that consists of some number of initial bits of an
> >        IP address which identifies the entire mobile network within the
> >        Internet topology. All nodes in a mobile network necessarily have
> >        an address named after this prefix.
> >
> >   draft-ietf-neno-terminology-00.txt
> >
> >      MNP
> >       An acronym for Mobile Network Prefix (defined in [Mobility])
> >
> > So, I think it's useless to define it here again in basic-support.
>
> that was deliberately added. I didnt want a normative
> reference to a draft which is not controlled by this
> WG. what is the status of this draft in the Seamoby
> WG?
>
> Vijay
>
> _______________________________________________
> Seamoby mailing list
> [email protected]
> https://www1.ietf.org/mailman/listinfo/seamoby
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.