<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>RE: Quick question on a Request for package registration</TITLE>
<META content="MSHTML 5.00.2920.0" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT color=#0000ff face=Arial><SPAN class=573012514-08032001>Yes, you must
specify both when defining a package.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial><SPAN
class=573012514-08032001></SPAN></FONT> </DIV>
<DIV><FONT color=#0000ff face=Arial><SPAN
class=573012514-08032001>Brian</SPAN></FONT></DIV>
<BLOCKQUOTE
style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; PADDING-LEFT: 5px">
<DIV align=left class=OutlookMessageHeader dir=ltr><FONT face=Tahoma
size=2>-----Original Message-----<BR><B>From:</B> Kevin Gorey
[mailto:kgorey@nortelnetworks.com]<BR><B>Sent:</B> Thursday, March 08, 2001
6:52 AM<BR><B>To:</B> 'ian.park@vf.vodafone.co.uk'; Tom-PT Taylor;
'iana@iana.org'<BR><B>Cc:</B> 'megaco@fore.com';
'itu-sg16@mailbag.cps.intel.com'<BR><B>Subject:</B> RE: Quick question on a
Request for package registration<BR><BR></DIV></FONT>
<P><FONT color=#0000ff face=Arial size=2>Dear all,</FONT> </P>
<P><FONT color=#0000ff face=Arial size=2>As I've been involved in 3GPP working
group discussions regarding these 3GPP H.248 extentions, I'd like to provide
some additional information/comments.</FONT></P>
<P><FONT color=#0000ff face=Arial size=2>Although the 3GPP working groups view
is that the 3GPP specification that contains the package definations in
question is 95% complete. In my opinion these packages are not currently
technically stable, during the last meeting the technical details for the
encoding of the TFO package were not agreed.</FONT></P>
<P><FONT color=#0000ff face=Arial size=2>Additionally, there is the open issue
within 3GPP as to whether these 3GPP H.248 specifications should be specified
for both text and binary encodings, or whether only one encoding type should
be chosen. </FONT></P>
<P><FONT color=#0000ff face=Arial size=2>However from reading clause 13.1 of
H.248 (reproduced below) it seems that its a mandatory requirement to specify
both a text and binary encoding of additional packages.</FONT></P>
<P><FONT color=#0000ff face=Arial size=2>13.1
Packages</FONT> <BR><FONT color=#0000ff face=Arial size=2>The following
considerations SHALL be met to register a package with IANA:</FONT> <BR><FONT
color=#0000ff face=Arial size=2>1) A unique
string name, unique serial number and version number is registered for each
package. The string name is used with text encoding. The serial number shall
be used with binary encoding. Serial Numbers 60000-64565 are reserved for
private use. Serial number 0 is reserved.</FONT></P>
<P><FONT color=#0000ff face=Arial size=2>..."</FONT> </P>
<P><FONT color=#0000ff face=Arial size=2>Regards,</FONT> </P>
<P><FONT color=#0000ff face=Arial size=2>Kevin.</FONT> </P><BR><BR><BR>
<P><FONT face=Tahoma size=2>-----------------</FONT> <BR><FONT face=Tahoma
size=2>Kevin Gorey</FONT> <BR><FONT face=Tahoma size=2>Nortel Networks, UMTS
Strategic Product Planning</FONT> <BR><FONT face=Tahoma size=2>Tel: +44
(0)1628 434606</FONT> <BR><FONT face=Tahoma size=2>Fax: +44 (0)1628
434034</FONT> <BR><FONT face=Tahoma size=2>kgorey@nortelnetworks.com</FONT>
</P><BR>
<UL>
<P><FONT face=Arial size=1>-----Original Message-----</FONT> <BR><B><FONT
face=Arial size=1>From: </FONT></B> <FONT face=Arial
size=1>ian.park@vf.vodafone.co.uk [SMTP:ian.park@vf.vodafone.co.uk]</FONT>
<BR><B><FONT face=Arial size=1>Sent: </FONT></B> <FONT face=Arial
size=1>Wednesday, March 07, 2001 10:40 AM</FONT> <BR><B><FONT face=Arial
size=1>To: </FONT></B> <FONT face=Arial
size=1>Taylor, Tom-PT [NORSE:B881:EXCH]; iana@iana.org</FONT> <BR><B><FONT
face=Arial size=1>Cc: </FONT></B> <FONT face=Arial
size=1>megaco@fore.com; itu-sg16@mailbag.cps.intel.com;
ian.park@vf.vodafone.co.uk</FONT> <BR><B><FONT face=Arial
size=1>Subject: </FONT></B> <FONT
face=Arial size=1>RE: Quick question on a Request for package
registration</FONT> </P>
<P><FONT face=Arial size=2>Dear all</FONT> <BR><FONT face=Arial
size=2> </FONT> <BR><FONT face=Arial size=2>FWIW, I agree entirely with
Michelle's assessment. 3GPP specifications are</FONT> <BR><FONT face=Arial
size=2>*definitely* public documents (and we require that any document which
is</FONT> <BR><FONT face=Arial size=2>cited as a reference in a 3GPP
specification is, in turn, a publicly</FONT> <BR><FONT face=Arial
size=2>available document).</FONT> <BR><FONT face=Arial size=2> </FONT>
<BR><FONT face=Arial size=2>On Tom Taylor's point about the stability of the
specifications, we agreed</FONT> <BR><FONT face=Arial size=2>at last week's
working group meeting that the specifications are now ready</FONT> <BR><FONT
face=Arial size=2>for approval (which means that they will be brought under
a formal change</FONT> <BR><FONT face=Arial size=2>control system). They
will be presented for approval at the meeting of</FONT> <BR><FONT face=Arial
size=2>Technical Specification Group Core network next week (14 - 16 March)
in Palm</FONT> <BR><FONT face=Arial size=2>Springs, CA.</FONT> <BR><FONT
face=Arial size=2> </FONT> <BR><FONT face=Arial size=2>I hope this
helps.</FONT> <BR><FONT face=Arial size=2> </FONT> <BR><FONT face=Arial
size=2>Best regards</FONT> <BR><FONT face=Arial size=2> </FONT>
<BR><FONT face=Arial size=2>Ian Park</FONT> <BR><FONT face=Arial
size=2>___________________________________________________ </FONT><BR><FONT
face=Arial size=2>Ian Park</FONT> <BR><FONT face=Arial size=2>Chief
Engineer, Core Network Signalling Standards</FONT> <BR><FONT face=Arial
size=2>Vodafone Limited</FONT> <BR><FONT face=Arial size=2>*T: +44 1635 673
527 </FONT><BR><FONT face=Arial size=2>*F: +44 1635 233 562 </FONT><BR><FONT
face=Arial size=2>?E: ian.park@vf.vodafone.co.uk </FONT><BR><FONT face=Arial
size=2>___________________________________________________ </FONT><BR><FONT
face=Arial size=2> </FONT> </P>
<P><FONT face=Arial size=2>-----Original Message-----</FONT> <BR><FONT
face=Arial size=2>From: Tom-PT Taylor [<U></U></FONT><U><FONT color=#0000ff
face=Arial size=2><A
href="mailto:taylor@nortelnetworks.com">mailto:taylor@nortelnetworks.com</A></FONT></U><FONT
face=Arial size=2>]</FONT> <BR><FONT face=Arial size=2>Sent: 26 February
2001 10:50</FONT> <BR><FONT face=Arial size=2>To: IANA</FONT> <BR><FONT
face=Arial size=2>Cc: megaco@fore.com; itu-sg16@mailbag.intel.com;
ian.park@vf.vodafone.co.uk</FONT> <BR><FONT face=Arial size=2>Subject: RE:
Quick question on a Request for package registration</FONT> </P><BR><BR>
<P><FONT face=Arial size=2>3GPP is a public forum, and I believe their
packages would be viewed as</FONT> <BR><FONT face=Arial size=2>public.
I'll note that it is desirable that the packages be considered</FONT>
<BR><FONT face=Arial size=2>technically stable (though perhaps subject to
some editing and minor</FONT> <BR><FONT face=Arial size=2>adjustment) before
they are registered.</FONT> </P>
<P><FONT face=Arial size=2>I've copied various parties for coordination
purposes. </FONT></P>
<P><FONT face=Arial size=2>> -----Original Message----- </FONT><BR><FONT
face=Arial size=2>> From: IANA [</FONT><U> <FONT color=#0000ff face=Arial
size=2><A
href="mailto:iana@iana.org">mailto:iana@iana.org</A></FONT></U><FONT
face=Arial size=2> <</FONT><U><FONT color=#0000ff face=Arial size=2><A
href="mailto:iana@iana.org">mailto:iana@iana.org</A></FONT></U><FONT
face=Arial size=2>> ] </FONT><BR><FONT face=Arial size=2>> Sent:
Friday, February 23, 2001 5:28 PM </FONT><BR><FONT face=Arial size=2>>
To: Taylor, Tom-PT [NORSE:B881:EXCH] </FONT><BR><FONT face=Arial size=2>>
Subject: FW: Quick question on a Request for package registration
</FONT><BR><FONT face=Arial size=2>> </FONT><BR><FONT face=Arial
size=2>> </FONT><BR><FONT face=Arial size=2>> Tom, </FONT><BR><FONT
face=Arial size=2>> </FONT><BR><FONT face=Arial size=2>> Quick
question. Which range should these packages be registered in?
</FONT><BR><FONT face=Arial size=2>> Do I need to ask the applicants if
these are public or private? </FONT><BR><FONT face=Arial size=2>>
</FONT><BR><FONT face=Arial size=2>> From the RFC: </FONT><BR><FONT
face=Arial size=2>> Public packages MUST be given serial numbers in the
range 0x0001 to </FONT><BR><FONT face=Arial size=2>> 0x7fff.
Private packages MUST be given serial numbers in the range </FONT><BR><FONT
face=Arial size=2>> 0x8000 to 0xffff. </FONT><BR><FONT face=Arial
size=2>> </FONT><BR><FONT face=Arial size=2>> Thanks for any
help. If there is someone better to ask, please let me
</FONT><BR><FONT face=Arial size=2>> know. Don't want to bug you :)
</FONT><BR><FONT face=Arial size=2>> </FONT><BR><FONT face=Arial
size=2>> Michelle </FONT><BR><FONT face=Arial size=2>> IANA
</FONT><BR><FONT face=Arial size=2>> </FONT><BR><FONT face=Arial
size=2>> **************************************************************
</FONT><BR><FONT face=Arial size=2>> *********** </FONT><BR><FONT
face=Arial size=2>> </FONT><BR><FONT face=Arial size=2>> Hi there
</FONT><BR><FONT face=Arial size=2>> </FONT><BR><FONT face=Arial
size=2>> I am the editor for a 3rd Generation Partnership Project
</FONT><BR><FONT face=Arial size=2>> (3GPP) protocol </FONT><BR><FONT
face=Arial size=2>> specification which defines extensions to the
H.248/MeGaCo </FONT><BR><FONT face=Arial size=2>> protocol; I have
</FONT><BR><FONT face=Arial size=2>> pasted in a copy of the "Scope"
clause of this specification below. </FONT><BR><FONT face=Arial size=2>>
</FONT><BR><FONT face=Arial size=2>> "The present document describes the
protocol to be used on </FONT><BR><FONT face=Arial size=2>> the Media
Gateway </FONT><BR><FONT face=Arial size=2>> Controller (MGC) - Media
Gateway (MGW) interface. The Media Gateway </FONT><BR><FONT face=Arial
size=2>> Controllers covered in this specification are the MSC server
</FONT><BR><FONT face=Arial size=2>> and the GMSC </FONT><BR><FONT
face=Arial size=2>> server. The basis for this protocol is the
H.248/MEGACO protocol as </FONT><BR><FONT face=Arial size=2>> specified
in ITU-T and IETF. The BICC architecture as </FONT><BR><FONT face=Arial
size=2>> described in ITU-T </FONT><BR><FONT face=Arial size=2>>
Q.1902 [7]-[11] and 3G TS 23.205 [3] defines the usage of </FONT><BR><FONT
face=Arial size=2>> this protocol. </FONT><BR><FONT face=Arial
size=2>> This specification describes the changes to H.248/MEGACO
</FONT><BR><FONT face=Arial size=2>> which are needed to </FONT><BR><FONT
face=Arial size=2>> handle 3GPP specific traffic cases. This is done by
using the </FONT><BR><FONT face=Arial size=2>> H.248/MEGCO
</FONT><BR><FONT face=Arial size=2>> standard extension mechanism.
</FONT><BR><FONT face=Arial size=2>> The present document is valid for a
3rd generation PLMN </FONT><BR><FONT face=Arial size=2>> (UMTS) complying
</FONT><BR><FONT face=Arial size=2>> with Release 2000 and later. "
</FONT><BR><FONT face=Arial size=2>> We need to define three new packages
for this specification, </FONT><BR><FONT face=Arial size=2>> and as the
</FONT><BR><FONT face=Arial size=2>> custodians of the package
identifiers you are the people I </FONT><BR><FONT face=Arial size=2>>
need to contact </FONT><BR><FONT face=Arial size=2>> to ask for the
package numbers! </FONT><BR><FONT face=Arial size=2>> </FONT><BR><FONT
face=Arial size=2>> I have pasted in the first part of the definition of
each </FONT><BR><FONT face=Arial size=2>> package below. </FONT><BR><FONT
face=Arial size=2>> </FONT><BR><FONT face=Arial size=2>>
13.1.1 IuUP package.
</FONT><BR><FONT face=Arial size=2>> PackageID: 3giuup (0x####)
</FONT><BR><FONT face=Arial size=2>> [Editor's note: PackageID to be
allocated by IANA] </FONT><BR><FONT face=Arial size=2>> Version: 1
</FONT><BR><FONT face=Arial size=2>> Extends: None </FONT><BR><FONT
face=Arial size=2>> This package identifies that the Iu User Plane is
used for </FONT><BR><FONT face=Arial size=2>> the termination.
</FONT><BR><FONT face=Arial size=2>> It also contains some parameters for
the Iu User Plane </FONT><BR><FONT face=Arial size=2>> functions in the
MGW. </FONT><BR><FONT face=Arial size=2>> The Iu User Plane is active in
both directions independently </FONT><BR><FONT face=Arial size=2>> of the
Stream </FONT><BR><FONT face=Arial size=2>> Mode. </FONT><BR><FONT
face=Arial size=2>> 13.1.2
Circuit Switched Data package </FONT><BR><FONT face=Arial size=2>>
PackageID: 3gcsd (0x####) </FONT><BR><FONT face=Arial size=2>> [Editor's
note: PackageID to be allocated by IANA] </FONT><BR><FONT face=Arial
size=2>> Version: 1 </FONT><BR><FONT face=Arial size=2>> Extends: None
</FONT><BR><FONT face=Arial size=2>> This package contains the
information needed to be able to </FONT><BR><FONT face=Arial size=2>>
support GSM and </FONT><BR><FONT face=Arial size=2>> UMTS Circuit
Switched Data from the media gateway. </FONT><BR><FONT face=Arial
size=2>> 13.1.3 TFO package
</FONT><BR><FONT face=Arial size=2>> PackageID: 3gtfoc (0x####)
</FONT><BR><FONT face=Arial size=2>> [Editor's note: PackageID to be
allocated by IANA] </FONT><BR><FONT face=Arial size=2>> Version: 1
</FONT><BR><FONT face=Arial size=2>> Extends: None </FONT><BR><FONT
face=Arial size=2>> This package defines events and properties for Tandem
Free </FONT><BR><FONT face=Arial size=2>> Operation (TFO)
</FONT><BR><FONT face=Arial size=2>> control. TFO uses inband signalling
and procedures for </FONT><BR><FONT face=Arial size=2>> Transcoders to
enable </FONT><BR><FONT face=Arial size=2>> compressed speech to be
maintained between a tandem pair of </FONT><BR><FONT face=Arial size=2>>
transcoders. </FONT><BR><FONT face=Arial size=2>> This package allows an
MGW which has inserted a transcoder to </FONT><BR><FONT face=Arial
size=2>> support TFO. </FONT><BR><FONT face=Arial size=2>> Can you
please let me know how I should go on from here to </FONT><BR><FONT
face=Arial size=2>> have the package </FONT><BR><FONT face=Arial
size=2>> numbers allocated? If you need any further information,
</FONT><BR><FONT face=Arial size=2>> please contact me. </FONT><BR><FONT
face=Arial size=2>> </FONT><BR><FONT face=Arial size=2>> Best regards
</FONT><BR><FONT face=Arial size=2>> </FONT><BR><FONT face=Arial
size=2>> Ian Park </FONT><BR><FONT face=Arial size=2>>
</FONT><BR><FONT face=Arial size=2>>
___________________________________________________ </FONT><BR><FONT
face=Arial size=2>> Ian Park </FONT><BR><FONT face=Arial size=2>>
Chief Engineer, Core Network Signalling Standards </FONT><BR><FONT
face=Arial size=2>> Vodafone Limited </FONT><BR><FONT face=Arial
size=2>> *T: +44 1635 673 527 </FONT><BR><FONT face=Arial size=2>> *F:
+44 1635 233 562 </FONT><BR><FONT face=Arial size=2>> *E:
ian.park@vf.vodafone.co.uk </FONT><BR><FONT face=Arial size=2>>
___________________________________________________ </FONT><BR><FONT
face=Arial size=2>> </FONT><BR><FONT face=Arial size=2>>
</FONT><BR><FONT face=Arial size=2>>
</FONT></P></UL></BLOCKQUOTE></BODY></HTML>