[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ipng
Subject:    Fw: draft-ietf-dnsop-dontpublish-unreachable-02.txt
From:       "Jim Fleming" <jfleming () anet ! com>
Date:       2002-01-23 16:54:04
[Download RAW message or body]

From: "Larson, Matt" <mlarson@verisign.com>
To: <dnsop@cafax.se>
Sent: Wednesday, January 23, 2002 7:50 AM
Subject: RE: draft-ietf-dnsop-dontpublish-unreachable-02.txt


> > a very rough draft for IPv6 counterpart is attached.  
> >      please let me
> > know if you want to integrate two it one, or want to handle them
> > separately.
> 
> We're in the process of adding IPv6 support to the com/net/org registry.  We
> are currently planning on disallowing name servers (i.e., glue AAAA records)
> containing IPv4-mapped or IPv4-compatible addresses.  This plan would be in
> conflict with Itojun's proposed section 2.5, which allows IPv4-compatible
> addresses (though I noticed the parenthetical caveat).
> 
> I would grateful if some IPv6 experts weighed in on this issue.
> 
> Thanks,
> 
> Matt
> --
> Matt Larson <mlarson@verisign.com>
> VeriSign Global Registry Services

----- Original Message ----- 
From: "Jim Fleming" <jfleming@anet.com>
To: <richard.tindal@neulevel.biz>
Cc: <enoss@tucows.com>; <cgomes@verisign.com>; <david@new.net>
Sent: Sunday, January 20, 2002 9:27 PM
Subject: http://www.opensrs.org/archives/discuss-list/0201/0806.html


> http://www.opensrs.org/archives/discuss-list/0201/0806.html
> Subject: RE: Re[2]: .biz Transfer Policy
> From: Tindal, Richard (richard.tindal@neulevel.biz)
> ----
> 
> You missed a key point which is that you are just contracted
> for the Proof-of-Concept registry operations on the "toy", legacy,
> IPv4 Internet. That just helps to develop a base of names for the
> production services on the Next Generation Internet. The 8 top
> TLDs are shown below. .BIZ has a ways to go before it can
> compete with .COM.
> 
>       0:201 .COM 
>       1:158 .CLUB 
>       2:143 .FAMILY 
>       3:219 .INFO 
>       4:58 .LLC
>      
>       5:194 .INC
>      
>       6:171 .TV
>      
>       7:195 .CHURCH
>      
> 
> 
> The Next Generation DNS architecture, focuses on reliability,
> higher transaction rates, database driven updates and the ability
> to have "flavors" of a TLD. As an example, we will be able to
> have a .COM zone with or without the adult content names.
> http://www.dot-biz.com/IPv8/Papers/LameDCache/
> 
> Keep everyone posted on your Proof-of-Concept progress.
> The 8 TLDs above should be enough for now to test the
> production-grade designs.
> 
> Jim Fleming
> 2002:[IPv4]:000X:03DB
> http://www.IPv8.info
> 
> 

--------------------------------------------------------------------
IETF IPng Working Group Mailing List
IPng Home Page:                      http://playground.sun.com/ipng
FTP archive:                      ftp://playground.sun.com/pub/ipng
Direct all administrative requests to majordomo@sunroof.eng.sun.com
--------------------------------------------------------------------
[prev in list] [next in list] [prev in thread] [next in thread]