[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Wg-ipv6-guide] (ToC11) Database Registration
hi Everyone,
Sorry for not responding earlier to some of the queries that have come
up - I have just returned from vacation. Some thoughts below...
> Thanks Nakagawa-san for listing up the contents.
> I think all the major points are coverered but added a few comments.
>
> > - Definition of Database
> > In this policy, "database" means the Whois Databases of RIRs and NIRs.
> > At present, APNIC, RIPE-NCC, ARIN and LACNIC have databases.
> This situation may change over time with new RIRs and NIRs providing
> the database, so how about we simply refer to them as RIR/NIR database
> without specifying the organizations?
>
> Or, if you think it is better to be more specific, may be we can refer
> to only APNIC and NIRs since this is the guidelines for AP?
I would suggest that since these guidelines are being written specifically
to assist people in the AP region in understanding the global policy
document, it would be preferable to specify RIR and NIR databases.
> > These databases are accessible by not only RIRs but also any end site
> > on the IPv4 Internet.
> >
> >
> > - The organization responsible for registration
> > (1) Allocation
> > Each RIR is responsible for registering initial and subsequent
> > allocation information in a database. Typical example is the /32
> > or /31 allocations to ISPs.
> >
> > (2) Assignment
> > (a) When an organization that is holding an address allocation
> > makes assignments, this organization is responsible for
> > registering the assignment. Typical example of this organization
> > is ISP.
> > (b) When an organization makes an assignment through downstream
> > ISP, this organization is responsible for registering the
> > assignment.
> >
> > So, LIRs need some rules or contracts between downstream ISPs in
> > order to receive assignment information.
> I think it's a good idea to clarify the authority for registering
> allocations and assginments.
>
> However, I am not sure about the assignment policy via downstream
> ISPs. Before commenting on this part, I would like to confirm the
> interpretation of the policy first.
>
> Which of the following applies in IPv6?
>
> a) Only LIRs can register assignments for downstream ISP customers
> b) Only downstream ISP can register assignments for its customers
> c) Case by case. Depends on how you set the maintainer
>
> In IPv4, I believe it is case c). Whichever the case is in IPv6, I
> think is helpful to describe it in the document as Nakagawa-san has.
The LIR has ultimate responsibility for the address range they are
allocated. They can set whatever policy they wish using the maintainers.
However it is generally expected that a downstream ISP is able to
register the assignments - should they wish to do so.
> > - Items to be registered
> > http://www.apnic.net/db/ref/attributes/attributes-inet6num.html
> >
> >
> > - Deadline of the registration
> > As soon as possible after allocating or assigning. (<--correct?)
> It's good to state somewhere in the document that registerations
> should be made as soon as possible, but since there is no specific
> deadline, I'm not sure if we need a seperate section for this.
There is no deadline so i am not sure this is an appropriate heading.
As a guideline it is strongly recommendated that registration is
done as soon as possible after the assignment or sub-allocation. it
might also be worth mentioning that this can be done via MyAPNIC.
Note also that shortly LIRs will have the option to privately
register assignments and sub-allocations (according to policy proposal
http://www.apnic.net/docs/policy/proposals/prop-007-v001.html which
has just been approved by the EC).
[snip]
> > - Registration grater then /48
> > For example, the organization which has assigned /47 have to register
> > the /47 block in the database.
> I suppose you mean registrations "including and greater than /48?"
or equal to or longer than?
Anne
--
