[6bone] pTLA request NDSOFTWARE - review closes 23 October 2002

[John Fraizer]

On 20 Oct 2002, Nicolas DEFFAYET wrote:

> > > All tech contact in NDSoftware's whois have a root access on each
> > > routers. They understand v4/v6 routing, unix administration,... 
> > > 
> > 
> > Wow.  You're a trusting soul there.  SUDU is your friend, Dude.  You might
> > want to look at the man page for it.
> 
> Sudo is very limited.
> We trust our technical staff.

Sudu will do anything you tell it to do.  That is moot though.  I didn't
expect you to take advise from those who have been running production
networks for a decade.


> > week because our routers are overloaded with BGP sessions.  We've decided
> > to drop all of our BGP peers who are using reserved ASNs." -- Something
> > like that?
> 
> Now, please forgot the problem of delete of peer with private ASN on our
> routers.
> 
> It's not a world and public problem.

Nicolas, welcome to the real world.  You desire to become an equal peer
with other pTLA/sTLA entities.  You want to join the elite Default Free
Zone club.  I am happy to say that we _do_ have some standards and those
who don't meet those standards are, in my humble opinion, not welcome.

Your treatment of your CURRENT peers is the only guideline we have to go
on to determine how tactfully you may interact with other DFZ peers.

> > > Ops, fixed. 
> > > 
> > > I have forgot to add "ifconfig lo add 3ffe:81f1:2:1::1/64" in the init
> > > scripts of parcr1.fr.ndsoftwarenet.net. 
> > 
> > Wow.  I can't imagine trying to explain that to one of my customers.  This
> > is all about attention to detail Nicolas.  So, you get your own pTLA and
> > people start actually listening to and propagating your announcements and
> > you "forget" a little thing like applying an access-list or route-map to
> > a peering session.  Guess what?  Your lack of attention to detail does
> > more than embarrass you.  It can cause service effecting outages for a
> > whole ton of OTHER people.
> 
> 
> All humains do errors.
> You have do too many errors...

Sorry Nicolas.  I hate to break it to you.  You're not going to find an
instance where my lack of attention to detail has caused routing
instability for ANYONE.  Yes.  I have made errors in my lifetime but, when
it comes to routing, _REAL_ engineers check their work.

> 
> > role:         IPv6-FR NOC
> > address:      IPv6-FR
> > address:      57 rue du president Wilson
> > address:      92300 Levallois-Perret
> > address:      France
> > phone:        +33 671887502
> > 
> > role:         NDSoftware NOC
> > address:      NDSoftware
> > address:      57 rue du president Wilson
> > address:      92300 Levallois-Perret
> > address:      France
> > phone:        +33 671887502
> > 
> > 
> > I'm sorry Nicolas.  Providing address space to YOURSELF doesn't
> > count!  Sheesh! 
> 
> 
> NDSoftware and IPv6-FR are in the same building but aren't the same
> legal organization.
> I'm a network administrator for the both.

And would this be your home by some strange coincidence?

> > Don't you think that a tunnel-broker housed in Wichita, KS, USA would be
> > better served by a 6bone pTLA *IN* the USA?  Also, with your current
> > peering policy change, isn't this site going to get NIXED?  I note their
> > use of a Reserved ASN.
> 
> They don't find any help somewhere...
> 
> We don't only provide a block, we provide a small tech support, help in
> tunnel and zebra configuration,....

They didn't look very hard.


> > 
> > Now, since you obviously don't care if your peers maintain their ipv6-site
> > objects or even HAVE them for that matter, how is it that you are abiding
> > by RFC2772, Section 5?
> > 
> 
> Check all others pTLA request, you have the same problem.
> 
> You can't force a peer to register a whois entry...
> 
> Our whois is always updated.


(1) We're not talking about other peoples pTLA request.  We're talking
about YOURS.

(2) We do NOT have the same problem with the ipv6-site object.  There may
be discrepancy of listed routing protocols or the other site may not have
UPDATED _THEIR_ ipv6-site object but, the ENTERZONE ipv6-site object does
NOT reference NON-EXISTENT objects as yours does.  Referencing
non-existent objects simply pollutes the 6bone database with inaccurate
information.

(3) You are correct.  You can't force a peer to register a whois
entry.  You *CAN* refuse to peer with entities who refuse to register, at
minimum, IPv6-site, Inet6num and Mntner objects as specifically _REQUIRED_
by section 5 of RFC2772.  If they have a problem with this policy, you can
simply point them to the RFC and tell them that if you peer with them, you
have to create an entry in your ipv6-site object referencing
them.  Without their having _REAL_ objects for you to reference, and
especially if you just make up ipv6-site objects to reference in yours,
you are in violation of RFC2772, section 7, subsection 1, paragraph A.


Let me lead you through Section 9 of RFC2772:

9.  Common rules enforcement for the 6bone

   Participation in the 6Bone is a voluntary and benevolent undertaking.
   However, participating sites are expected to adhere to the rules and
   policies described in this document in order to maintain the 6Bone as
   a quality tool for the deployment of, and transition to, IPv6
   protocols and the products implementing them.

   The following is in support of policing adherence to 6Bone rules and
   policies:

   1. Each pTLA site has committed to implement the 6Bone's rules and
      policies, and SHOULD try to ensure they are adhered to by sites
      within their administrative control, i.e. those to who prefixes
      under their respective pTLA prefix have been delegated.


Hrm...  I'm betting that this applies to your peers who haven't registered
the appropriate objects.




   2. When a site detects an issue, it SHOULD first use the 6Bone
      registry to contact the site maintainer and work the issue.


Now, how do you suppose that I should go about contacting an entity whom I
can NOT look up in the 6bone registry?



   3. If nothing happens, or there is disagreement on what the right
      solution is, the issue SHOULD be brought to the 6Bone Operations
      Group.


Guess what Nicolas.  I detected problems with your application for a
pTLA.  I detected problems with your ipv6-site object referencing
NON-EXISTENT objects.  I brought these issues to your attention.  Nothing
has been done to correct these problems and as a matter of fact, instead
of attending to the problems, you start pointing the finger at everyone
else and then go on to say "you can't force a peer to register a whois
entry."



---
John Fraizer
EnterZone, Inc

"I'm Nicolas DEFFAYET, i have 4 years, i got every day to school, and i
play with my FisherPrice routers and i destroy all 6bone." - Nicolas
DEFFAYET, 20 October 2002.