ITU-T is not "reluctant" to create the references to external
organisations. It has made a set of rules for such references, and has
then failed so far to get them to work.
The rules are contained in Recommendation A.5 published in 1998.
ITU-T SG9 recently tried to use these rules, and fell foul of the very
precise nature of these rules.
The recent ITU-T SG chairmen's meeting discussed this, and I believe
identified that the rules were not meant to be this restrictive, and not
meant to be applied on a per recommendation / reference basis, i.e. once
IETF had been identified as a suitable organisation fulfilling all the
rules, it did not repeatedly need to prove its suitability.
I understand SG9 will be attempting more Recommendation references to
external organisations in the near future, and in ITU-T SG11, we will
also be attempting to do this.
Keith Drage
Siemens Communication Systems Limited
Nottingham UK
> -----Original Message-----
> From: Jim Toga [SMTP:jim.toga@INTEL.COM]
> Sent: Thursday, February 04, 1999 4:04 PM
> To: ITU-SG16(a)MAILBAG.INTEL.COM
> Subject: Re: TPKT in H.225.0
>
> I am working on some (initial) text for the Implementers Guide. I
> will
> welcome additions/modifications at the Rapportours meeting......
>
>
> jimt.
>
> At 02:03 PM 2/4/99 +0100, Derks, Frank wrote:
> >Hi Tom,
> >
> >I couldn't find it either and I suspect that it couldn't be in
> because the
> >ITU is very reluctant to reference any non-ITU material. Furthermore,
> >RFC1006 encompasses a lot more than just the bit(s) that are used for
> >H.225.0, so even referring to this RFC does not clarify it all. I
> think some
> >work should be spent on this.
> >
> >Frank
> >
> >-----Original Message-----
> >From: Tom-PT Taylor [mailto:taylor@NORTELNETWORKS.COM]
> >Sent: 02 February 1999 22:12
> >To: ITU-SG16(a)MAILBAG.INTEL.COM
> >Subject: Re: TPKT in H.225.0
> >
> >
> >I'd swear the reference to RFC1006 used to be in H.225.0 Appendix D,
> but I
> >can't find it there now.
> >
> >> -----Original Message-----
> >> From: Derks, Frank [SMTP:F.Derks@PBC.BE.PHILIPS.COM]
> >> Sent: Tuesday, February 02, 1999 4:05 AM
> >> To: ITU-SG16(a)MAILBAG.INTEL.COM
> >> Subject: Re: TPKT in H.225.0
> >>
> >> Hi Paul,
> >>
> >> I received two responses to my question, one from you and one from
> Tom
> >> Taylor. The fact that there are at least two people that know about
> it
> >> (and
> >> several dozens more that have actually implemented the protocol
> stacks),
> >> makes it hard to believe that this is an "oversight" in the
> >> recommendation.
> >> In fact, not knowing about this makes it impossible to implement an
> >> interoperable protocol stack! Shouldn't action be taken to get this
> into
> >> the
> >> recommendation ASAP (e.g. through the Implementor's Guide)?
> >>
> >> Regards,
> >>
> >> Frank
> >>
> >> -----Original Message-----
> >> From: Paul Long [mailto:Plong@SMITHMICRO.COM]
> >> Sent: 01 February 1999 18:50
> >> To: ITU-SG16(a)MAILBAG.INTEL.COM
> >> Subject: Re: TPKT in H.225.0
> >>
> >>
> >> TPKT is defined in RFC 1006. Not identifying TPKT was an oversight
> that
> >> has
> >> never been fixed in the Recommendation.
> >>
> >> Paul Long
> >> Smith Micro Software, Inc.
> >
> +1-503-264-8816(voice) Intel - Hillsboro, OR
> mailto:jim.toga@intel.com mailto:james.toga@ties.itu.int
> PGP keyID 36 07 86 49 7D 74 DF 57 50 CB BA 32 08 9C 7C 41
