RE: [NSI-RRP] IP Address Uniqueness

From: Hollenbeck, Scott (shollenb@netsol.com)
Date: Fri Jun 30 2000 - 06:50:04 EDT

  • Next message: Patrik Fältström : "RE: [NSI-RRP] IP Address Uniqueness"

    Rick,

    While the GRRP requirements draft defines management of contact objects as a
    mandatory protocol feature, the draft also says that a thin registry does
    not have to support management of contacts.

    Scott Hollenbeck
    Network Solutions, Inc. Registry

    -----Original Message-----
    From: Rick H Wesson [mailto:wessorh@ar.com]
    Sent: Friday, June 30, 2000 12:48 AM
    To: Kent Crispin
    Cc: 'RRP List'
    Subject: Re: [NSI-RRP] IP Address Uniqueness

    Kent,

    you raze several issues that I certainly have no answer for:

      o where does the policy belong, there are poliicy decision made
        in protocols and even RRP 1.1.0 has them, which ones should
        we make as part of gRRP's requirements.

      o I don't have an answer on notification but I will tru to come up
        with some proposals.

      o correct me if I'm wrong but doesn't the requirirements got gRRP
        define the registry as "thick" since contact objects are required?

    -rick

    On Thu, 29 Jun 2000, Kent Crispin wrote:

    > On Thu, Jun 29, 2000 at 05:19:24PM -0700, Rick H Wesson wrote:
    > >
    > > Scott,
    > >
    > > this will only encourage the creation of A records in each gTLD for
    > > folks that automaticly create NS records children NS of a given zone in
    a
    > > TLD.
    >
    > Rick, I think you are mixing two levels -- the protocol specification
    > level, and the registry policy level. A registry may indeed have a
    > policy that prevents multiple names for a nameserver IP address -- it
    > may implement that check, and a number of others in its database, and
    those
    > policies may be good things. But the question is whether they should
    > be specified in the protocol.
    >
    > [...]
    >
    > > I would also propose that a gRRP have a notification mechanism to
    prevent
    > > someone from using and IP address of an NS that I own. I would like to
    > > prevent folks from using my NS w/o permission.
    >
    > It might be reasonable for the RRP to have a notification mechanism that
    > goes to the end user (though at this point it doesn't make sense to me
    > to have such a thing -- seems to break the "RR" part of "RRP"), but it
    > should be a general mechanism, and not tied to this specific policy
    > issue.
    >
    > --
    > Kent Crispin "Do good, and you'll be
    > kent@songbird.com lonesome." -- Mark Twain
    > ---------
    > See http://www.nsiregistry.com/maillist/rrp/
    > for message archives and subscription management information.
    >

    ---------
    See http://www.nsiregistry.com/maillist/rrp/
    for message archives and subscription management information.
    ---------
    See http://www.nsiregistry.com/maillist/rrp/
    for message archives and subscription management information.



    This archive was generated by hypermail 2b29 : Mon Jul 03 2000 - 13:38:48 EDT