[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Wg-ipv6-guide] (ToC 7.2) Documentation required (fwd)
Hi all,
Good idea. I think it's useful to supply this information as long as
it's clearly stated that it's not mandatory.
It's more of a formatting issue rather than the contents, but may I
suggest to create a seperate section such as " Supplementary
Documentation"(Name can be different)? Then, we can state about the
vendor/model name here.
I thought putting it under "Documentation Required" section make give
the impression that they are mandatory.
Izumi
From: Toshiyuki Hosaka <hosaka@nic.ad.jp>
Subject: Re: [Wg-ipv6-guide] (ToC 7.2) Documentation required (fwd)
Date: Fri, 16 Jan 2004 16:52:10 +0900
> Hi Son, Maruta-san, and all,
>
> Thank you for your comments. I agree with Maruta-san that vendor/model
> name is not *mandatory*. However there has been the case that IRs asks
> such information as Son wrote.
>
> So tentatively I would like to propose this as below. Please comment.
>
> ----------------------------
> 7.2 Documentation required
>
> When LIRs request their initial IPv6 address allocation to RIR/NIR,
> LIRs are requested to provide designated request form as well as the
> following information.
>
> - Network diagram
> - Network equipment information. This is to ensure LIR has a plan to
> implement IPv6 ready infrastructure.
>
> (Model/Vendor name is not mandatory but there may be a case that
> RIR/NIR asks those information in some cases.(e.g. if LIRs
> require a plenty of pool address such as CATV/ADSL operator.))
>
> - Approximate deployment date.
> - Service plan (Web hosting, Access service, etc)
> ---------------------------------
>
> Thanks and best regards,
> Toshi
>
>
> From: John Tran <john@apnic.net>
> Subject: Re: [Wg-ipv6-guide] (ToC 7.2) Documentation required (fwd)
> Date: Wed, 14 Jan 2004 17:58:17 +1000 (EST)
>
> > Hi all,
> >
> > Thank you very much for Toshi-san to produce the draft. I would like to provide some general
> > information on what type of information we need when evaluating.
> >
> > I agree with Toru-san that sometime a network is sufficient to understand on how address
> > space will be used. I am, however, also see why Toshi-san require other information as well.
> >
> > For example if the request is for an organisation infrastructure and a few difference services
> > that does not require knowledge of equipment details like web-hosting, transit, and etc. This
> > kind of request we can easily understand and make the decision with or without the diagram.
> > However, for the case where an organisation is going to provide services such as ADSL, Cable modem, and etc where there is a requirement of large pool of address space to be assigned then it is
> > necesary for IR to understand how many and what kind of equipment the organisation has purchased
> > so that IR can accurately access the address requirement.
> >
> > Therefore in general not all information are needed for all application but it is totally depending
> > on each application. As such maybe we need to reword the document to reflect this.
> >
> > Thanks
> >
> > son
> > APNIC
> >
> >
> >
> >
> > > > > Date: Tue, 13 Jan 2004 09:58:57 +0900
> > > > > From: Toru Maruta <to-maruta@kddi.com>
> > > > > To: hosaka@nic.ad.jp, wg-ipv6-guide@lists.apnic.net
> > > > > Subject: Re: [Wg-ipv6-guide] (ToC 7.2) Documentation required
> > > > >
> > > > > Hi Hosaka san,
> > > > >
> > > > > I believe the following example is the actual required documents
> > > > > to get an initial ipv6 address allocation. However I was curious
> > > > > why network equipment information (i.e., vendor name, model name)
> > > > > was necessary. Sometimes network equipment change due to the
> > > > > tender process. I also doubt that allocation decision changes
> > > > > depending on the actual equipment vendor. I have a feeling that
> > > > > network diagram (topology) information is sufficient for
> > > > > allocation decision, and vendor/model information may not be
> > > > > mandatory.
> > > > >
> > > > > Toru Maruta
> > > > >
> > > > >
> > > > > <20040109191021P.hosaka@nic.ad.jp> の、
> > > > > "[Wg-ipv6-guide] (ToC 7.2) Documentation required" において、
> > > > > "Toshiyuki Hosaka <hosaka@nic.ad.jp>"さんは書きました：
> > > > >
> > > > > > Dear all,
> > > > > >
> > > > > > Please see the draft below. Regarding 7.2.1, we would like to list
> > > > > > better example so I especially appreciate APNIC's comment who has the
> > > > > > experience to evaluate the real IPv6 request. Comments from others are
> > > > > > welcome of course.
> > > > > >
> > > > > > Looking forward to hearing from you all.
> > > > > >
> > > > > > ---------------------------------------------------------------------
> > > > > > 7.2 Documentation required
> > > > > >
> > > > > > When LIRs request their initial IPv6 address allocation to RIR/NIR,
> > > > > > LIRs are requested to provide designated request form as well as the
> > > > > > following information.
> > > > > >
> > > > > > - Network diagram
> > > > > > - Network equipment information. This is to ensure LIR has a plan to
> > > > > > implement IPv6 ready infrastructure.
> > > > > > + Vendor name (such as CISCO, HITACHI..)
> > > > > > + Model name
> > > > > > - Approximate deployment date.
> > > > > > - Service plan (Web hosting, Access service, etc)
> > > > > >
> > > > > > ---------------------------------------------------------------------
> > > > > > 7.2.1 Examples
> > > > > > Following is the example of the documentation required. These are
> > > > > > for reference for the ISPs.
> > > > > >
> > > > > > - ADSL/Cable providers
> > > > > > + Network diagram
> > > > > > + CMTS information (Quantity, model name)
> > > > > > + Approximate deployment date
> > > > > > + The number of existing (or projected) customers
> > > > > >
> > > > > > - mobile phone operators, GPRS
> > > > > > + Network diagram
> > > > > > + Network equipment information
> > > > > > + Approximate deployment date
> > > > > > + The number of existing (or projected) customers
> > > > > >
> > > > > > - transit providers
> > > > > > + Network diagram
> > > > > > + Network equipment information
> > > > > > + Approximate deployment date
> > > > > > + The number of existing (or projected) customers
> > > > > >
> > > > > > - multi-national enterprises
> > > > > > - educational institutions
> > > > > > + Network diagram
> > > > > > + Network equipment information
> > > > > > + Approximate deployment date
> > > > > > + The number of organizations to which LIRs assign /48s
> > > > > >
> > > > > > --------------------------------------------------------------------
> > > > > >
> > > > > > Best regards,
> > > > > > Toshi
> > > > > > --
> > > > > > Toshiyuki Hosaka <hosaka@nic.ad.jp>
> > > > > > IP Department, Japan Network Information Center (JPNIC)
> > > > > > tel: +81-(0)3-5297-2311 fax: +81-(0)3-5297-2312
> > > > > >
> > > > > >
> > > > > > _______________________________________________
> > > > > > Wg-ipv6-guide mailing list
> > > > > > Wg-ipv6-guide@lists.apnic.net
> > > > > > http://mailman.apnic.net/mailman/listinfo/wg-ipv6-guide
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Toru Maruta
> > > > > KDDI Corporation
> > > > >
> > > > > _______________________________________________
> > > > > Wg-ipv6-guide mailing list
> > > > > Wg-ipv6-guide@lists.apnic.net
> > > > > http://mailman.apnic.net/mailman/listinfo/wg-ipv6-guide
> > > > >
> > > >
> > > >
> > >
> >
> >
>
> _______________________________________________
> Wg-ipv6-guide mailing list
> Wg-ipv6-guide@lists.apnic.net
> http://mailman.apnic.net/mailman/listinfo/wg-ipv6-guide
>
