[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Request to advance rfc4214(bis) to standards-track through ADsponsorship



Pekka,


On 3/30/07 7:54 AM, "ext Pekka Savola" <pekkas@netcore.fi> wrote:

[snip]
> 
> FWIW I personally haven't seen sufficient justification (e.g., the
> amount and the kind of deployments; the number of implementations that
> currently ship ISATAP as specified by the RFC; the amount of required
> revisions to the specification) to move ISATAP to the standards track.

I have to say I don't really agree with you. ISATAP is implemented in
multiple instances (Windows, routers, etc.). Thus, I would say there should
be enough support to make the document Proposed Standard.

I think the question is if it is worth the trouble at this point. And is
there some protocol evolution needed based on the practical experiences with
the protocol. You and me cannot answer that. I think the people shipping the
products can. 

I also would like to know is the "ISATAP" in the products the same as the
"ISATAP" in RFC4214? If ISATAP != ISATAP it would really be worth while
updating the document and bring the deployed ISATAP to PS.

> 
> Even if there was a high-level decision to do so, the process should
> take a number of months at the very least to ensure proper review has
> been done.

Perhaps "number of months" sounds a bit harsh - however, even with a
sponsoring AD there needs to be community review of the document.

Cheers,

Jonne.

-- 
Jonne Soininen
Nokia

Tel: +358 40 527 46 34
E-mail: jonne.soininen@nokia.com