Re: [Enum] DRAFT-ALLOCCHIO-GSTN-02.TXT Updated version

Hallo,

> I am pretty bemused at this - I seem to have missed the earlier ones.
> The Application ADs suggested it?

yes sir!

> What exactly does this add to RFC2806?
> It doesn't seem to update 2806, so I don't understand how I use this,
> or where.

I think you missed the main point here. RFC2806, RFC3191, RFC3192, and a
large number of rfc-to-be from the VPIM WG in the RFC Editor queue now all
use the syntax and specification contained into
DRAFT-ALLOCCHIO-GSTN-02.TXT and thus are all compatible with it. Thus this
document does not add or updated any of them at all (all authors of the 
above documents are those who contributed to this I-D).

However the specifications are embedded into RFCs whose title and 
purpouse is not to sepcify how you write in text a dial string sequence, 
and this creates continuously the "re-invent the wheel" problem, and the 
ADs and IESG has to send back specifications asking the authors to use 
the existing standard specification. If there is a single "collection" 
document with a sensible title, and which is free from other definitions 
which might confuse the reader, the "keeping the coherence" job is easier.
 
> In particular, the phone-context stuff in 2806 is there for a good reason
> - the phone string could well be sent to Finland (inside an email, for
> instance). This is not going to work if one uses local phone string
> format (with 001 to call the U.S.).

Local Phone string can work only "locally", and global-phone ones do 
their job globally. If you think the text is not clear enough, we can try 
to clarify it.

> Hey, I'm sure you don't have anything else to do before 2300 MET, right? :).

... I'm just waiting the kernel to rebuild after I included IPv6 on my 
workstation... thus I have some time...

:-)

Regards
Claudio

Received on Friday, 22 February 2002 05:20:12 UTC