[6bone] RFC2772 rewrite

[Daniel Austin]

Hi Robert / other 6bone folk,

----- Original Message -----
From: "Robert J. Rockell" <rrockell@sprint.net>
To: "Nicolas DEFFAYET" <nicolas.deffayet@ndsoftware.net>
Cc: "Paul Aitken" <paitken@cisco.com>; "6BONE List" <6bone@mailman.isi.edu>
Sent: Wednesday, November 13, 2002 4:56 PM
Subject: Re: [6bone] RFC2772 rewrite


> I would agree that sometimes, guaranteeing resolution in a timely manner is
> difficult. Learning curves aside, bugs in all forms of software, from
> end-system, to DNS, to Router, can provide for delay times in excess of 24
> hours.  this is permissible, so long as the pTLA can scope the problem to
> minimize impact on the global 6bone, right?

A definitive resolution may take more than 24 hours, but as long as a provider is actively trying to fix a problem i think we are
achieving what we want.  Not all problems can be resolved in 24 hours and certainly not in a development environment.  It doesnt
take much to reply to an email with a couple of updates along the way :-)

However, as per the earlier e-mails, everyone can get problems and in this kind of environment i think they're unavoidable.  What we
need to steer away from is "one man bands" making themselves appear larger than they are and then becoming overloaded with problems.
I know we have the multiple contacts in the 6bone guidelines - but it's pretty simple to make a name and email address up!  (in case
anyone feels like checking mine - my other contact is a listed director of the company too!)
It's fun to play a big company, but it hinders development on this level.


With Thanks,

Daniel Austin,
Managing Director,
kewlio.net Limited.
<daniel@kewlio.net>

> Thanks
> Rob Rockell
> SprintLink
> (+1) 703-689-6322
> -----------------------------------------------------------------------
>
> On 13 Nov 2002, Nicolas DEFFAYET wrote:
>
> ->On Wed, 2002-11-13 at 16:32, Paul Aitken wrote:
> ->Paul,
> ->
> ->>  > If I don't hear anyone complain in 24 hours (good number to use)
> ->>  > we'll stick that in there :)
> ->>
> ->> *complain*
> ->>
> ->> While I appreciate the sentiment behind this suggestion, and wouldn't be
> ->> surprised to find that most folks on the list meet the requirement, I'd
> ->> expect that there are some folks who do actually have a life and
> ->> actually do non work-related things at the weekend <gasp!> and I
> ->> wouldn't want to discourage that in any way!
> ->
> ->>From RFC2772:
> ->
> ->   2. The pTLA Applicant MUST have the ability and intent to provide
> ->       "production-quality" 6Bone backbone service. Applicants must
> ->       provide a statement and information in support of this claim.
> ->       This MUST include the following:
> ->
> ->
> ->      a. A support staff of two persons minimum, three preferable, with
> ->          person attributes registered for each in the ipv6-site object
> ->          for the pTLA applicant.
> ->
> ->
> ->A pTLA is managed by many people.
> ->
> ->If a network is correctly managed, there is always someone available for
> ->solve technical problems.
> ->
> ->> Besides, there are plenty of other times when we're out of touch for
> ->> more than 24 hours, during which time we expect our networks to run
> ->> happily without our constant supervision, right?
> ->>
> ->> As Daniel said:
> ->>
> ->>  > I don't think that 24hours is bad for a *response* - maybe not
> ->>  > resolution though.
> ->>
> ->> An autoresponder or ticketing system would meet the response requirement
> ->> without actually dealing with the problem in any way :-(
> ->>
> ->> So what are we trying to achieve? To force the pTLA holder to respond,
> ->> or to encourage them to resolve the technical issue? What would happen
> ->> if it took 48 hours to respond to an issue - would the time police
> ->> reject the holder's pTLA? Will someone volunteer to be "big brother" to
> ->> ensure timely responses?
> ->
> ->Autoresponder or ticketing system don't solve the problem of reply and
> ->the technical problem.
> ->
> ->Best Regards,
> ->
> ->Nicolas DEFFAYET, NDSoftware
> ->NOC Website: http://noc.ndsoftwarenet.com/
> ->FNIX6: http://www.fnix6.net/
> ->
>
> _______________________________________________
> 6bone mailing list
> 6bone@mailman.isi.edu
> http://mailman.isi.edu/mailman/listinfo/6bone
>