<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>C-277: H.248.1 Compatibility</TITLE>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2900.3086" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><STRONG><EM><FONT color=#0000ff>Hello Albrecht,</FONT></EM></STRONG></DIV>
<DIV><STRONG><EM><FONT color=#0000ff></FONT></EM></STRONG> </DIV>
<DIV><STRONG><EM><FONT color=#0000ff>I have a question about one
sentence in the added text proposed by you -- "<SPAN lang=EN-GB
style="FONT-SIZE: 12pt; LAYOUT-GRID-MODE: line; FONT-FAMILY: 'Times New Roman'; mso-bidi-font-size: 10.0pt; mso-fareast-font-family: 'MS Mincho'; mso-ansi-language: EN-GB; mso-fareast-language: EN-US; mso-bidi-language: AR-SA">Any
MG registration is starting with protocol version 1</SPAN>", why is only version
1 instead of 2 or 3? In my understanding, it depends on the highest version
implemented by MG.</FONT></EM></STRONG></DIV>
<DIV><STRONG><EM><FONT color=#0000ff></FONT></EM></STRONG> </DIV>
<DIV><STRONG><EM><FONT color=#0000ff>
Regards, Yangbo</FONT></EM></STRONG></DIV>
<DIV><STRONG><EM><FONT color=#0000ff></FONT></EM></STRONG> </DIV>
<BLOCKQUOTE dir=ltr
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style="FONT: 9pt 宋体"><FONT face="Times New Roman">----- Original Message
----- </FONT></DIV>
<DIV style="BACKGROUND: #e4e4e4; FONT: 9pt 宋体; font-color: black"><FONT
face="Times New Roman"><B>From:</B> </FONT><A
title=Albrecht.Schwarz@alcatel-lucent.de
href="mailto:Albrecht.Schwarz@alcatel-lucent.de"><FONT
face="Times New Roman">Schwarz Albrecht</FONT></A><FONT
face="Times New Roman"> </FONT></DIV>
<DIV style="FONT: 9pt 宋体"><FONT face="Times New Roman"><B>To:</B> </FONT><A
title=Christian.Groves@nteczone.com
href="mailto:Christian.Groves@nteczone.com"><FONT
face="Times New Roman">Christian.Groves@nteczone.com</FONT></A><FONT
face="Times New Roman"> </FONT></DIV>
<DIV style="FONT: 9pt 宋体"><FONT face="Times New Roman"><B>Cc:</B> </FONT><A
title=itu-sg16@lists.packetizer.com
href="mailto:itu-sg16@lists.packetizer.com"><FONT
face="Times New Roman">itu-sg16@lists.packetizer.com</FONT></A><FONT
face="Times New Roman"> ; </FONT><A title=linyangbo@huawei.com
href="mailto:linyangbo@huawei.com"><FONT
face="Times New Roman">linyangbo@huawei.com</FONT></A><FONT
face="Times New Roman"> ; </FONT><A title=CWaitzmann@alcatel-lucent.de
href="mailto:CWaitzmann@alcatel-lucent.de"><FONT
face="Times New Roman">CWaitzmann@alcatel-lucent.de</FONT></A><FONT
face="Times New Roman"> ; </FONT><A
title=Juergen.Stoetzer-Bradler@alcatel-lucent.de
href="mailto:Juergen.Stoetzer-Bradler@alcatel-lucent.de"><FONT
face="Times New Roman">Juergen.Stoetzer-Bradler@alcatel-lucent.de</FONT></A><FONT
face="Times New Roman"> ; </FONT><A title=jerker.zetterlund@ericsson.com
href="mailto:jerker.zetterlund@ericsson.com"><FONT
face="Times New Roman">Jerker Zetterlund (TN/EAB</FONT></A><FONT
face="Times New Roman"> </FONT></DIV>
<DIV style="FONT: 9pt 宋体"><FONT face="Times New Roman"><B>Sent:</B> Monday,
June 25, 2007 7:43 PM</FONT></DIV>
<DIV style="FONT: 9pt 宋体"><FONT face="Times New Roman"><B>Subject:</B> C-277:
H.248.1 Compatibility</FONT></DIV>
<DIV><BR></DIV><!-- Converted from text/rtf format -->
<P><FONT size=2>Hello Christian, all,</FONT> </P>
<P><FONT size=2>like the proposal concerning forward & backward
compatibility rules. Did add some text with regards to the compatibilty
mechanism(s), which are specific to H.248 (and thus worth to be
mentioned).</FONT></P>
<P><FONT size=2>Best regards,</FONT> <BR><FONT size=2>Albrecht</FONT>
</P><BR><BR>
<P><FONT color=#000000 size=2><<T05-SG16-C-0277r1 H.248
Compatibility.doc>> </FONT><BR><FONT size=2>####</FONT> </P>
<P><FONT color=#000000 size=2>Hello Albrecht, Keith,</FONT> </P>
<P><FONT color=#000000 size=2>Thanks for the reference to Q.1400. I think it
was these fundamentals of </FONT><BR><FONT color=#000000 size=2>compatibility
for ISUP and DSS that lead to the original definition of </FONT><BR><FONT
color=#000000 size=2>the version negotiation and protocol enhancement rules in
H.248.1. At </FONT><BR><FONT color=#000000 size=2>the time of writing
H.248.1v1 there was involvement from a number of </FONT><BR><FONT
color=#000000 size=2>people involved in the work of SG11.</FONT> </P>
<P><FONT color=#000000 size=2>I think the general principles of Q.1400 are
in-line with what is being </FONT><BR><FONT color=#000000 size=2>used in
H.248.1 so at this level it can be used. I agree some of the </FONT><BR><FONT
color=#000000 size=2>specific examples aren't relevant for H.248.1. I'll try
to propose some </FONT><BR><FONT color=#000000 size=2>clarifying text for the
Q.3/16 meeting. I don't intend to write a thesis </FONT><BR><FONT
color=#000000 size=2>on the matter, I intend to stick making simple rules
applicable for </FONT><BR><FONT color=#000000 size=2>protocol, packages and
profiles.</FONT> </P>
<P><FONT color=#000000 size=2>Regards, Christian</FONT> </P>
<P><FONT color=#000000 size=2>Albrecht Schwarz wrote:</FONT> <BR><FONT
color=#000000 size=2>> [Like to open a separate thread on compatibility
rules for H.248, think</FONT> <BR><FONT color=#000000 size=2>> this is a
more general topic in comparison to the Ia specific IP realm</FONT> <BR><FONT
color=#000000 size=2>> indication mechanism.]</FONT> <BR><FONT
color=#000000 size=2>></FONT> <BR><FONT color=#000000 size=2>> Keith,
thanks for the pointer to Q.1400, believe that the clause about</FONT>
<BR><FONT color=#000000 size=2>> compatibility rules is a good baseline for
correspondent definitions for</FONT> <BR><FONT color=#000000 size=2>>
H.248.</FONT> <BR><FONT color=#000000 size=2>> I think additional explicit
text about compatibility rules in H.248.1, e.g.</FONT> <BR><FONT color=#000000
size=2>> in clause 12, would be beneficial.</FONT> <BR><FONT color=#000000
size=2>></FONT> <BR><FONT color=#000000 size=2>> We may not directly
reuse Q.1400 for H.248 (in my understanding) because</FONT> <BR><FONT
color=#000000 size=2>> a) Q.1400 is for ASN.1 defined protocols (and H.248
has also ANBF defined</FONT> <BR><FONT color=#000000 size=2>> grammar for
text encoding mode),</FONT> <BR><FONT color=#000000 size=2>> b) Q.1400
focus is SS7 and DSS1, or</FONT> <BR><FONT color=#000000 size=2>> c) H.248
integrated version/profile mechanisms.</FONT> <BR><FONT color=#000000
size=2>></FONT> <BR><FONT color=#000000 size=2>> Christian, think that
your proposal is a good baseline. Could you submit it</FONT> <BR><FONT
color=#000000 size=2>> as input to next Q.3/16 meeting?</FONT> <BR><FONT
color=#000000 size=2>></FONT> <BR><FONT color=#000000 size=2>>
Albrecht</FONT> <BR><FONT color=#000000 size=2>></FONT> <BR><FONT
color=#000000 size=2>></FONT> <BR><FONT color=#000000 size=2>></FONT>
<BR><FONT color=#000000
size=2>>
</FONT></P>
<P><FONT color=#000000
size=2>>
"Drage,
Keith
</FONT></P>
<P><FONT color=#000000
size=2>>
\(Keith\)"
To: "Schwarz, Albrecht \(Albrecht\)"
<albrecht.schwarz@alcatel-lucent.de>,
</FONT></P>
<P><FONT color=#000000
size=2>>
<drage@alcatel-l
<TISPAN_WG3@LIST.ETSI.ORG>
</FONT></P>
<P><FONT color=#000000
size=2>>
ucent.com>
cc:
</FONT></P>
<P><FONT color=#000000
size=2>>
Subject: RE: H.248 Ia Profile Version
2
</FONT></P>
<P><FONT color=#000000
size=2>>
24.04.2007
12:07
</FONT></P>
<P><FONT color=#000000
size=2>>
</FONT></P>
<P><FONT color=#000000 size=2>></FONT> <BR><FONT color=#000000
size=2>></FONT> <BR><FONT color=#000000 size=2>></FONT> <BR><FONT
color=#000000 size=2>></FONT> <BR><FONT color=#000000 size=2>> The
compatibility definitions in ITU-T are all in Q.1400.</FONT> <BR><FONT
color=#000000 size=2>></FONT> <BR><FONT color=#000000 size=2>>
Regards</FONT> <BR><FONT color=#000000 size=2>></FONT> <BR><FONT
color=#000000 size=2>> Keith</FONT> <BR><FONT color=#000000
size=2>></FONT> <BR><FONT color=#000000 size=2>>
</FONT><BR><FONT color=#000000 size=2>>> -----Original
Message-----</FONT> <BR><FONT color=#000000 size=2>>> From: Albrecht
Schwarz [</FONT><A
href="mailto:Albrecht.Schwarz@ALCATEL-LUCENT.DE"><U></U><U><FONT color=#0000ff
size=2>mailto:Albrecht.Schwarz@ALCATEL-LUCENT.DE</FONT></U></A><FONT
color=#000000 size=2>]</FONT> <BR><FONT color=#000000 size=2>>> Sent:
Tuesday, April 24, 2007 1:08 AM</FONT> <BR><FONT color=#000000 size=2>>>
To: TISPAN_WG3@LIST.ETSI.ORG</FONT> <BR><FONT color=#000000 size=2>>>
Subject: Re: H.248 Ia Profile Version 2</FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>> Bruno</FONT>
<BR><FONT color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>> </FONT><BR><FONT color=#000000
size=2>>>> My understanding is that backward compatibility in the
work item</FONT> <BR><FONT color=#000000
size=2>>>> </FONT><BR><FONT
color=#000000 size=2>>> description was intended to refer to the
ability</FONT> <BR><FONT color=#000000 size=2>>>
</FONT><BR><FONT color=#000000 size=2>>>> for version n+1 to
understand version n without requiring version</FONT> <BR><FONT color=#000000
size=2>>>> </FONT><BR><FONT
color=#000000 size=2>>> negotiation to occur before. This is usually
what</FONT> <BR><FONT color=#000000 size=2>>>
</FONT><BR><FONT color=#000000 size=2>>>> is meant in other ITU-T and
ETSI standards dealing with signalling.</FONT> <BR><FONT color=#000000
size=2>>>> </FONT><BR><FONT
color=#000000 size=2>>> Couldn't find any appropriate definition for
"backward</FONT> <BR><FONT color=#000000 size=2>>> compatibility" in
ITU-T & ETSI (like the one for codecs from H.262).</FONT> <BR><FONT
color=#000000 size=2>>></FONT> <BR><FONT color=#000000 size=2>>>
There are signalling protocols with and without a version</FONT> <BR><FONT
color=#000000 size=2>>> negotiation mechanism. The understanding of
"backward</FONT> <BR><FONT color=#000000 size=2>>> compatibility" might
be slightly different for both</FONT> <BR><FONT color=#000000 size=2>>>
categories. Guess the protocols without a version negotiation</FONT> <BR><FONT
color=#000000 size=2>>> method are the majority like the capability set
based ITU-T</FONT> <BR><FONT color=#000000 size=2>>> protocols like e.g.
INAP, BICC or Q.2630.x.</FONT> <BR><FONT color=#000000 size=2>>> H.248
belongs to the category with an</FONT> <BR><FONT color=#000000 size=2>>>
a) integral mechanism for protocol version negotiation and in</FONT> <BR><FONT
color=#000000 size=2>>> addition a</FONT> <BR><FONT color=#000000
size=2>>> b) mechanism for profile negotiation</FONT> <BR><FONT
color=#000000 size=2>>> and also</FONT> <BR><FONT color=#000000
size=2>>> c) a multi profile mode capability (H.248.18).</FONT>
<BR><FONT color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>> The used protocol capabilities are related to the lifetime
of</FONT> <BR><FONT color=#000000 size=2>>> the H.248 Control
Association (CA), starting the negotiation</FONT> <BR><FONT color=#000000
size=2>>> at CA establishment.</FONT> <BR><FONT color=#000000
size=2>>> Capability upgrade procedures may lead to a re-new or</FONT>
<BR><FONT color=#000000 size=2>>> re-establishment of the CA.</FONT>
<BR><FONT color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>> A definition for "backward compatibility" for H.248 CAs
might</FONT> <BR><FONT color=#000000 size=2>>> therefore different to
other protocols without such mechanisms.</FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>> We got four WIs
for H.248 Profiles, - a MG registration with</FONT> <BR><FONT color=#000000
size=2>>> the correspondent ProfileID is part of a profile
specification.</FONT> <BR><FONT color=#000000 size=2>>> Saying that, the
meaning of backward compatibility in the WI</FONT> <BR><FONT color=#000000
size=2>>> description means that the MG registers with Ia/2 in my
opinion.</FONT> <BR><FONT color=#000000 size=2>>> In case of a fallback
requirement to Ia/1, then current draft</FONT> <BR><FONT color=#000000
size=2>>> my be extended for H.248.18 support (but this requires
a</FONT> <BR><FONT color=#000000 size=2>>> contribution).</FONT>
<BR><FONT color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>> Albrecht</FONT> <BR><FONT color=#000000 size=2>>></FONT>
<BR><FONT color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>></FONT>
<BR><FONT color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>></FONT>
<BR><FONT color=#000000
size=2>>>
Christian Groves</FONT> <BR><FONT color=#000000 size=2>>></FONT>
<BR><FONT color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>>
<Christian.Groves@NT
To:</FONT> <BR><FONT color=#000000 size=2>>>
TISPAN_WG3@LIST.ETSI.ORG</FONT> <BR><FONT color=#000000 size=2>>></FONT>
<BR><FONT color=#000000
size=2>>>
ECZONE.COM>
cc:</FONT> <BR><FONT color=#000000 size=2>>></FONT> <BR><FONT
color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>>
Subject:</FONT> <BR><FONT color=#000000 size=2>>> Re: H.248 Ia Profile
Version 2</FONT> <BR><FONT color=#000000 size=2>>></FONT> <BR><FONT
color=#000000
size=2>>>
23.04.2007 09:55</FONT> <BR><FONT color=#000000 size=2>>></FONT>
<BR><FONT color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>>
Please respond to</FONT> <BR><FONT color=#000000 size=2>>></FONT>
<BR><FONT color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>>
Christian Groves</FONT> <BR><FONT color=#000000 size=2>>></FONT>
<BR><FONT color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>></FONT>
<BR><FONT color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>></FONT>
<BR><FONT color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>> Hello
Bruno,</FONT> <BR><FONT color=#000000 size=2>>></FONT> <BR><FONT
color=#000000 size=2>>> What does "ability for version n+1 to understand
version n"</FONT> <BR><FONT color=#000000 size=2>>> mean? Even in the
scenario we are talking about a MG with a</FONT> <BR><FONT color=#000000
size=2>>> version n+1 control association will understand the version
n</FONT> <BR><FONT color=#000000 size=2>>> message because the encoding
has not changed (thus backwards</FONT> <BR><FONT color=#000000 size=2>>>
compatible by the definition below) but it will reject it</FONT> <BR><FONT
color=#000000 size=2>>> because of new required functionality. Likewise
it seems that</FONT> <BR><FONT color=#000000 size=2>>> "before version
negotiation" has been prompted by the email</FONT> <BR><FONT color=#000000
size=2>>> discussion. For some, such mechanisms are integral for</FONT>
<BR><FONT color=#000000 size=2>>> compatibility mechanisms.</FONT>
<BR><FONT color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>> Do you have a reference to a general description of
"backwards</FONT> <BR><FONT color=#000000 size=2>>>
compatibility"? The term is used alot but I don't know any</FONT>
<BR><FONT color=#000000 size=2>>> description</FONT> <BR><FONT
color=#000000 size=2>>> other than that in H.248.1. For example H.248.1
section 11.3</FONT> <BR><FONT color=#000000 size=2>>> Negotiation of
Protocol Version offers rules for new versions. ie.</FONT> <BR><FONT
color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>> /When extending the protocol with new
versions, the</FONT> <BR><FONT color=#000000 size=2>>> following
rules</FONT> <BR><FONT color=#000000 size=2>>>
should be followed:/</FONT> <BR><FONT color=#000000
size=2>>> /1) Existing protocol elements, i.e.,
procedures, parameters,</FONT> <BR><FONT color=#000000
size=2>>> descriptor, property, values,
should/</FONT> <BR><FONT color=#000000 size=2>>>
/not be changed unless a protocol error needs to be</FONT> <BR><FONT
color=#000000 size=2>>> corrected or it</FONT> <BR><FONT color=#000000
size=2>>> becomes necessary to/</FONT> <BR><FONT
color=#000000 size=2>>> /change the operation of
the service that is being</FONT> <BR><FONT color=#000000 size=2>>>
supported by the</FONT> <BR><FONT color=#000000
size=2>>> protocol./</FONT> <BR><FONT
color=#000000 size=2>>> /2) The semantics of a
command, a parameter, a descriptor, a</FONT> <BR><FONT color=#000000
size=2>>> property, or a value should not
be/</FONT> <BR><FONT color=#000000 size=2>>>
/changed./</FONT> <BR><FONT color=#000000
size=2>>> /3) Established rules for formatting
and encoding messages and</FONT> <BR><FONT color=#000000
size=2>>> parameters should not be/</FONT>
<BR><FONT color=#000000 size=2>>>
/modified./</FONT> <BR><FONT color=#000000
size=2>>> /4) When information elements are
found to be obsolete they can be</FONT> <BR><FONT color=#000000
size=2>>> marked as not used./</FONT> <BR><FONT
color=#000000 size=2>>> /However, the identifier
for that information element</FONT> <BR><FONT color=#000000 size=2>>>
will be marked</FONT> <BR><FONT color=#000000
size=2>>> as reserved. In that way/</FONT>
<BR><FONT color=#000000 size=2>>> /it cannot be
used in future versions./</FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>> These rules
were adopted to ensure backwards compatibility. I</FONT> <BR><FONT
color=#000000 size=2>>> think these rules are equally applicable to the
case of</FONT> <BR><FONT color=#000000 size=2>>> profiles. When the MGC
and MG agree on the use of a control</FONT> <BR><FONT color=#000000
size=2>>> association they agree on the</FONT> <BR><FONT color=#000000
size=2>>> H.248.1 version and the profile (including version).</FONT>
<BR><FONT color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>> Regards, Christian</FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>> CHATRAS Bruno
RD-CORE-ISS wrote:</FONT> <BR><FONT color=#000000
size=2>>> </FONT><BR><FONT color=#000000
size=2>>>> Hello Chirstian,</FONT> <BR><FONT color=#000000
size=2>>>></FONT> <BR><FONT color=#000000 size=2>>>> My
understanding is that backward compatibility in the work item</FONT> <BR><FONT
color=#000000 size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>> description was intended to
refer to the ability for version</FONT> <BR><FONT color=#000000
size=2>>> n+1 to understand version n without requiring version</FONT>
<BR><FONT color=#000000 size=2>>> negotiation to occur before.</FONT>
<BR><FONT color=#000000 size=2>>> This is usually what is meant in other
ITU-T and ETSI</FONT> <BR><FONT color=#000000 size=2>>> standards
dealing with signalling.</FONT> <BR><FONT color=#000000
size=2>>> </FONT><BR><FONT color=#000000
size=2>>>> Best Regards,</FONT> <BR><FONT color=#000000
size=2>>>> Bruno</FONT> <BR><FONT color=#000000
size=2>>>></FONT> <BR><FONT color=#000000 size=2>>>>
-----Message d'origine-----</FONT> <BR><FONT color=#000000 size=2>>>>
De : Christian Groves [</FONT><A
href="mailto:Christian.Groves@NTECZONE.COM"><U></U><U><FONT color=#0000ff
size=2>mailto:Christian.Groves@NTECZONE.COM</FONT></U></A><FONT color=#000000
size=2>]</FONT> <BR><FONT color=#000000 size=2>>>> Envoyé : lundi 23
avril 2007 02:58</FONT> <BR><FONT color=#000000 size=2>>>> À :
TISPAN_WG3@LIST.ETSI.ORG</FONT> <BR><FONT color=#000000 size=2>>>>
Objet : Re: H.248 Ia Profile Version 2</FONT> <BR><FONT color=#000000
size=2>>>></FONT> <BR><FONT color=#000000 size=2>>>> Hello
Bruno,</FONT> <BR><FONT color=#000000 size=2>>>></FONT> <BR><FONT
color=#000000 size=2>>>> What was the definition of "backward
compatibility" that</FONT> <BR><FONT color=#000000
size=2>>>> </FONT><BR><FONT
color=#000000 size=2>>> the work item</FONT> <BR><FONT color=#000000
size=2>>> description assumed? It seems that people have
different</FONT> <BR><FONT color=#000000 size=2>>>
interpretations.</FONT> <BR><FONT color=#000000
size=2>>> </FONT><BR><FONT color=#000000
size=2>>>> Regards, Christian</FONT> <BR><FONT color=#000000
size=2>>>></FONT> <BR><FONT color=#000000 size=2>>>> CHATRAS
Bruno RD-CORE-ISS wrote:</FONT> <BR><FONT color=#000000
size=2>>>></FONT> <BR><FONT color=#000000
size=2>>>> </FONT><BR><FONT
color=#000000 size=2>>>>> This is version negotiation, not
backward compatibility.... Both</FONT> <BR><FONT color=#000000
size=2>>>>>
</FONT><BR><FONT color=#000000 size=2>>> approaches are valid protocol
design approaches and have</FONT> <BR><FONT color=#000000 size=2>>>
their pros and cons. However, the Work Item description</FONT> <BR><FONT
color=#000000 size=2>>> assumed "backward compatibility between version
1 and 2...</FONT> <BR><FONT color=#000000
size=2>>> </FONT><BR><FONT color=#000000
size=2>>>>> -----Message d'origine-----</FONT> <BR><FONT
color=#000000 size=2>>>>> De : Neal ZhuNing [</FONT><A
href="mailto:zhuning@HUAWEI.COM"><U></U><U><FONT color=#0000ff
size=2>mailto:zhuning@HUAWEI.COM</FONT></U></A><FONT color=#000000 size=2>]
Envoyé : vendredi 20</FONT> <BR><FONT color=#000000 size=2>>>>>
avril 2007 04:09 À : TISPAN_WG3@LIST.ETSI.ORG Objet : Re: H.248 Ia</FONT>
<BR><FONT color=#000000 size=2>>>>> Profile Version 2</FONT>
<BR><FONT color=#000000 size=2>>>>></FONT> <BR><FONT color=#000000
size=2>>>>> Agree Albrecht's state.</FONT>
<BR><FONT color=#000000 size=2>>>>> When a
BGF registers with a ProfileID "ETSI_BGF/1" 0r</FONT> <BR><FONT color=#000000
size=2>>>>> "ETSI_BGF/2",</FONT> <BR><FONT color=#000000
size=2>>>>>
</FONT><BR><FONT color=#000000 size=2>>> corresponding ia profile(ia/2
or ia/1) should be applied.</FONT> <BR><FONT color=#000000
size=2>>> </FONT><BR><FONT color=#000000
size=2>>>>> I think the Profile-based backward
compatibility</FONT> <BR><FONT color=#000000
size=2>>>>>
</FONT><BR><FONT color=#000000 size=2>>> between ia/2 and</FONT>
<BR><FONT color=#000000 size=2>>> ia/1 is based on their functions. Ia/2
can realize all the</FONT> <BR><FONT color=#000000 size=2>>> functions
of Ia/1, but new better methods can be used, even</FONT> <BR><FONT
color=#000000 size=2>>> it is mandatory.</FONT> <BR><FONT color=#000000
size=2>>> </FONT><BR><FONT color=#000000
size=2>>>>> BR</FONT> <BR><FONT color=#000000
size=2>>>>> Neal</FONT> <BR><FONT color=#000000
size=2>>>>></FONT> <BR><FONT color=#000000
size=2>>>>> -----Original Message-----</FONT> <BR><FONT
color=#000000 size=2>>>>> From: Albrecht Schwarz [</FONT><A
href="mailto:Albrecht.Schwarz@ALCATEL-LUCENT.DE"><U></U><U><FONT color=#0000ff
size=2>mailto:Albrecht.Schwarz@ALCATEL-LUCENT.DE</FONT></U></A><FONT
color=#000000 size=2>]</FONT> <BR><FONT color=#000000 size=2>>>>>
Sent: Thursday, April 19, 2007 6:50 PM</FONT> <BR><FONT color=#000000
size=2>>>>> To: TISPAN_WG3@LIST.ETSI.ORG</FONT> <BR><FONT
color=#000000 size=2>>>>> Subject: Re: H.248 Ia Profile Version
2</FONT> <BR><FONT color=#000000 size=2>>>>></FONT> <BR><FONT
color=#000000 size=2>>>>> [Sorry for using your initials as
abbreviation BC for backward</FONT> <BR><FONT color=#000000
size=2>>>>> compatibility :-)]</FONT> <BR><FONT color=#000000
size=2>>>>></FONT> <BR><FONT color=#000000 size=2>>>>>
I do agree to your statement.</FONT> <BR><FONT color=#000000
size=2>>>>></FONT> <BR><FONT color=#000000 size=2>>>>>
Important here is the "scope of the protocol" in my understanding.</FONT>
<BR><FONT color=#000000 size=2>>>>> There would be a compatibility
issue when the SPDF & BGF would</FONT> <BR><FONT color=#000000
size=2>>>>> operate</FONT> <BR><FONT color=#000000
size=2>>>>>
</FONT><BR><FONT color=#000000 size=2>>> Ia interface in the "NoProfile"
mode, i.e. the BGF would not</FONT> <BR><FONT color=#000000 size=2>>>
include the ServiceChangeProfile parameter for registration.</FONT> <BR><FONT
color=#000000 size=2>>> </FONT><BR><FONT
color=#000000 size=2>>>>> But the protocol scope is limited when
registering with a</FONT> <BR><FONT color=#000000
size=2>>>>>
</FONT><BR><FONT color=#000000 size=2>>> ProfileID</FONT> <BR><FONT
color=#000000 size=2>>> </FONT><BR><FONT
color=#000000 size=2>>>>> (as</FONT> <BR><FONT color=#000000
size=2>>>>>
</FONT><BR><FONT color=#000000 size=2>>> in case of ES 283 018). There
are then only "ETSI_BGF/1" or</FONT> <BR><FONT color=#000000 size=2>>>
"ETSI_BGF/2"</FONT> <BR><FONT color=#000000
size=2>>> </FONT><BR><FONT color=#000000
size=2>>>>> H.248 Messages between a single SPDF-BGF
tandem.</FONT> <BR><FONT color=#000000 size=2>>>>></FONT>
<BR><FONT color=#000000 size=2>>>>> I think that this is the
crucial point concerning "protcol</FONT> <BR><FONT color=#000000
size=2>>>>>
</FONT><BR><FONT color=#000000 size=2>>> scope" for</FONT> <BR><FONT
color=#000000 size=2>>> </FONT><BR><FONT
color=#000000 size=2>>>>> H.248</FONT> <BR><FONT color=#000000
size=2>>>>> interface: "Profile-less" vs "Profile-based" operated
H.248 Control</FONT> <BR><FONT color=#000000
size=2>>>>>
</FONT><BR><FONT color=#000000 size=2>>> Associations.</FONT> <BR><FONT
color=#000000 size=2>>> </FONT><BR><FONT
color=#000000 size=2>>>>> Albrecht</FONT> <BR><FONT color=#000000
size=2>>>>></FONT> <BR><FONT color=#000000
size=2>>>>></FONT> <BR><FONT color=#000000
size=2>>>>></FONT> <BR><FONT color=#000000
size=2>>>>></FONT> <BR><FONT color=#000000
size=2>>>>></FONT> <BR><FONT color=#000000
size=2>>>>>
"CHATRAS Bruno</FONT> <BR><FONT color=#000000 size=2>>>>></FONT>
<BR><FONT color=#000000
size=2>>>>>
RD-CORE-ISS"
To:</FONT> <BR><FONT color=#000000
size=2>>>>>
</FONT><BR><FONT color=#000000 size=2>>>
"Neal</FONT> <BR><FONT color=#000000 size=2>>>
</FONT><BR><FONT color=#000000 size=2>>>>> ZhuNing"
<zhuning@huawei.com>, <Albrecht.Schwarz@ALCATEL-LUCENT.DE></FONT>
<BR><FONT color=#000000
size=2>>>>>
<bruno.chatras@orange-f
cc:</FONT> <BR><FONT color=#000000 size=2>>>>>
<TISPAN_WG3@LIST.ETSI.ORG></FONT> <BR><FONT color=#000000
size=2>>>>></FONT> <BR><FONT color=#000000
size=2>>>>>
tgroup.com></FONT> <BR><FONT color=#000000
size=2>>>>>
</FONT><BR><FONT color=#000000 size=2>>> Subject: RE: H.248</FONT>
<BR><FONT color=#000000 size=2>>> Ia</FONT> <BR><FONT color=#000000
size=2>>> </FONT><BR><FONT color=#000000
size=2>>>>> Profile Version 2</FONT> <BR><FONT color=#000000
size=2>>>>></FONT> <BR><FONT color=#000000
size=2>>>>></FONT> <BR><FONT color=#000000
size=2>>>>>
19.04.2007 12:28</FONT> <BR><FONT color=#000000 size=2>>>>></FONT>
<BR><FONT color=#000000 size=2>>>>></FONT> <BR><FONT color=#000000
size=2>>>>></FONT> <BR><FONT color=#000000
size=2>>>>></FONT> <BR><FONT color=#000000
size=2>>>>></FONT> <BR><FONT color=#000000
size=2>>>>></FONT> <BR><FONT color=#000000
size=2>>>>></FONT> <BR><FONT color=#000000 size=2>>>>>
Adding a mandatory parameter to version n+1 of a protocol</FONT> <BR><FONT
color=#000000
size=2>>>>>
</FONT><BR><FONT color=#000000 size=2>>> means that</FONT> <BR><FONT
color=#000000 size=2>>> </FONT><BR><FONT
color=#000000 size=2>>>>> a</FONT> <BR><FONT color=#000000
size=2>>>>>
</FONT><BR><FONT color=#000000 size=2>>> message conforming to the
version n of this protocol is not a</FONT> <BR><FONT color=#000000
size=2>>> valid message for an implementation conforming to version
n+1</FONT> <BR><FONT color=#000000 size=2>>> of this protocol. Is not
this a compatobility issue?</FONT> <BR><FONT color=#000000
size=2>>> </FONT><BR><FONT color=#000000
size=2>>>>> BC</FONT> <BR><FONT color=#000000
size=2>>>>></FONT> <BR><FONT color=#000000 size=2>>>>>
-----Message d'origine-----</FONT> <BR><FONT color=#000000
size=2>>>>> De : Neal ZhuNing [</FONT><A
href="mailto:zhuning@huawei.com"><U></U><U><FONT color=#0000ff
size=2>mailto:zhuning@huawei.com</FONT></U></A><FONT color=#000000 size=2>]
Envoyé :</FONT> <BR><FONT color=#000000
size=2>>>>>
</FONT><BR><FONT color=#000000 size=2>>> jeudi 19 avril</FONT> <BR><FONT
color=#000000 size=2>>> </FONT><BR><FONT
color=#000000 size=2>>>>> 2007 11:55 À :
Albrecht.Schwarz@ALCATEL-LUCENT.DE; CHATRAS Bruno</FONT> <BR><FONT
color=#000000 size=2>>>>> RD-CORE-ISS Cc :
TISPAN_WG3@LIST.ETSI.ORG Objet : RE: H.248 Ia</FONT> <BR><FONT color=#000000
size=2>>>>> Profile Version 2</FONT> <BR><FONT color=#000000
size=2>>>>></FONT> <BR><FONT color=#000000 size=2>>>>>
Hi Albrecht, Bruno,</FONT> <BR><FONT color=#000000
size=2>>>>> In Ia/1, the hierarchical
termination name does not specifically</FONT> <BR><FONT color=#000000
size=2>>>>>
</FONT><BR><FONT color=#000000 size=2>>> mention that it is used to
identify the IP domain that a</FONT> <BR><FONT color=#000000 size=2>>>
termination is connected to, nor does it give an example of</FONT> <BR><FONT
color=#000000 size=2>>> the syntax associated with the "interface". So
maybe there is</FONT> <BR><FONT color=#000000 size=2>>> no backward
compatibility on this issue.</FONT> <BR><FONT color=#000000
size=2>>> </FONT><BR><FONT color=#000000
size=2>>>>> In Ia/2, the hierarchical termination name
may still be used to</FONT> <BR><FONT color=#000000
size=2>>>>>
</FONT><BR><FONT color=#000000 size=2>>> specify which physical or
logical interface a termination</FONT> <BR><FONT color=#000000 size=2>>>
should be associated with in the MG.</FONT> <BR><FONT color=#000000
size=2>>> </FONT><BR><FONT color=#000000
size=2>>>>> So, the hierarchical termination name mechanism is
same in Ia/1 and</FONT> <BR><FONT color=#000000
size=2>>>>>
</FONT><BR><FONT color=#000000 size=2>>> Ia/2, there is no backward
compatibility problem.</FONT> <BR><FONT color=#000000
size=2>>> </FONT><BR><FONT color=#000000
size=2>>>>> BR</FONT> <BR><FONT color=#000000
size=2>>>>> Neal</FONT> <BR><FONT color=#000000
size=2>>>>></FONT> <BR><FONT color=#000000 size=2>>>>>
-----Original Message-----</FONT> <BR><FONT color=#000000
size=2>>>>> From: Albrecht Schwarz [</FONT><A
href="mailto:Albrecht.Schwarz@ALCATEL-LUCENT.DE"><U></U><U><FONT color=#0000ff
size=2>mailto:Albrecht.Schwarz@ALCATEL-LUCENT.DE</FONT></U></A><FONT
color=#000000 size=2>]</FONT> <BR><FONT color=#000000 size=2>>>>>
Sent: Thursday, April 19, 2007 5:21 PM</FONT> <BR><FONT color=#000000
size=2>>>>> To: TISPAN_WG3@LIST.ETSI.ORG</FONT> <BR><FONT
color=#000000 size=2>>>>> Subject: Re: H.248 Ia Profile Version
2</FONT> <BR><FONT color=#000000 size=2>>>>></FONT> <BR><FONT
color=#000000 size=2>>>>> Bruno,</FONT> <BR><FONT color=#000000
size=2>>>>> when we discussed this, we couldn't see a violation of
the backward</FONT> <BR><FONT color=#000000
size=2>>>>>
</FONT><BR><FONT color=#000000 size=2>>> compatibility (BC)
principle.</FONT> <BR><FONT color=#000000
size=2>>> </FONT><BR><FONT color=#000000
size=2>>>>> The MG is registering either with Ia/1 or Ia/2, but
not with both</FONT> <BR><FONT color=#000000
size=2>>>>>
</FONT><BR><FONT color=#000000 size=2>>> profile versions (like in a
multiple profile mode), the used</FONT> <BR><FONT color=#000000
size=2>>> IP realm/domain indication mechanism is unambiguous.</FONT>
<BR><FONT color=#000000 size=2>>>
</FONT><BR><FONT color=#000000 size=2>>>>> The profile principle
is thus supporting BC targets.</FONT> <BR><FONT color=#000000
size=2>>>>> A single H.248 Control Association is either operated
with</FONT> <BR><FONT color=#000000
size=2>>>>>
</FONT><BR><FONT color=#000000 size=2>>> Ia/1 or Ia/2.</FONT> <BR><FONT
color=#000000 size=2>>> </FONT><BR><FONT
color=#000000 size=2>>>>> Do I overlook sth?</FONT> <BR><FONT
color=#000000 size=2>>>>></FONT> <BR><FONT color=#000000
size=2>>>>> Albrecht</FONT> <BR><FONT color=#000000
size=2>>>>></FONT> <BR><FONT color=#000000 size=2>>>>>
PS</FONT> <BR><FONT color=#000000 size=2>>>>> Above principle
is/may also used for other "capability upgrades",</FONT> <BR><FONT
color=#000000 size=2>>>>> like H.248.10 replacement by H.248.11 in
a next profile</FONT> <BR><FONT color=#000000
size=2>>>>>
</FONT><BR><FONT color=#000000 size=2>>> version, etc</FONT> <BR><FONT
color=#000000 size=2>>> </FONT><BR><FONT
color=#000000 size=2>>>>> etc</FONT> <BR><FONT color=#000000
size=2>>>>></FONT> <BR><FONT color=#000000
size=2>>>>></FONT> <BR><FONT color=#000000
size=2>>>>></FONT> <BR><FONT color=#000000
size=2>>>>></FONT> <BR><FONT color=#000000
size=2>>>>></FONT> <BR><FONT color=#000000
size=2>>>>>
CHATRAS Bruno</FONT> <BR><FONT color=#000000 size=2>>>>></FONT>
<BR><FONT color=#000000
size=2>>>>>
RD-CORE-ISS
To:</FONT> <BR><FONT color=#000000 size=2>>>>>
TISPAN_WG3@LIST.ETSI.ORG</FONT> <BR><FONT color=#000000
size=2>>>>></FONT> <BR><FONT color=#000000
size=2>>>>>
<bruno.chatras@ORANGE-F
cc:</FONT> <BR><FONT color=#000000 size=2>>>>></FONT> <BR><FONT
color=#000000
size=2>>>>>
TGROUP.COM></FONT> <BR><FONT color=#000000
size=2>>>>>
</FONT><BR><FONT color=#000000 size=2>>> Subject: H.248 Ia</FONT>
<BR><FONT color=#000000 size=2>>>
</FONT><BR><FONT color=#000000 size=2>>>>> Profile Version
2</FONT> <BR><FONT color=#000000 size=2>>>>></FONT> <BR><FONT
color=#000000 size=2>>>>></FONT> <BR><FONT color=#000000
size=2>>>>>
19.04.2007 11:12</FONT> <BR><FONT color=#000000 size=2>>>>></FONT>
<BR><FONT color=#000000
size=2>>>>>
Please respond to</FONT> <BR><FONT color=#000000
size=2>>>>></FONT> <BR><FONT color=#000000
size=2>>>>>
CHATRAS Bruno</FONT> <BR><FONT color=#000000 size=2>>>>></FONT>
<BR><FONT color=#000000
size=2>>>>>
RD-CORE-ISS</FONT> <BR><FONT color=#000000 size=2>>>>></FONT>
<BR><FONT color=#000000 size=2>>>>></FONT> <BR><FONT color=#000000
size=2>>>>></FONT> <BR><FONT color=#000000
size=2>>>>></FONT> <BR><FONT color=#000000
size=2>>>>></FONT> <BR><FONT color=#000000
size=2>>>>></FONT> <BR><FONT color=#000000
size=2>>>>></FONT> <BR><FONT color=#000000 size=2>>>>>
Ray, Wayne,</FONT> <BR><FONT color=#000000 size=2>>>>></FONT>
<BR><FONT color=#000000 size=2>>>>> I just had a look to the
Latest Draft of WI03098 (Ia</FONT> <BR><FONT color=#000000
size=2>>>>>
</FONT><BR><FONT color=#000000 size=2>>> profile Release</FONT>
<BR><FONT color=#000000 size=2>>>
</FONT><BR><FONT color=#000000 size=2>>>>> 2)</FONT> <BR><FONT
color=#000000
size=2>>>>>
</FONT><BR><FONT color=#000000 size=2>>> and saw that support of the new
IPDC package is mandatory</FONT> <BR><FONT color=#000000 size=2>>>
rather than optional.</FONT> <BR><FONT color=#000000
size=2>>> </FONT><BR><FONT color=#000000
size=2>>>>> This contradicts the Work Item description which
says</FONT> <BR><FONT color=#000000
size=2>>>>>
</FONT><BR><FONT color=#000000 size=2>>> explictly that</FONT> <BR><FONT
color=#000000 size=2>>> "The Ia profile version 2 shall maintain
backwards</FONT> <BR><FONT color=#000000 size=2>>> compatibility with
version 1." The meeting reports says that</FONT> <BR><FONT color=#000000
size=2>>> adding the IPDC package was indeed agreed but does not
say</FONT> <BR><FONT color=#000000 size=2>>> whether it should be
mandatory or optional.</FONT> <BR><FONT color=#000000 size=2>>> I
believe that we should either make this package optional or</FONT> <BR><FONT
color=#000000 size=2>>> made an attempt to modify the Work Item
description. I assume</FONT> <BR><FONT color=#000000 size=2>>> we can't
approve a deliverable which explicitly contradicts a</FONT> <BR><FONT
color=#000000 size=2>>> Work Item description.</FONT> <BR><FONT
color=#000000 size=2>>> </FONT><BR><FONT
color=#000000 size=2>>>>> BTW, what is the procedure for TB
approval of this modification.</FONT> <BR><FONT color=#000000
size=2>>>>> There</FONT> <BR><FONT color=#000000
size=2>>>>>
</FONT><BR><FONT color=#000000 size=2>>> does not seem to be any CR
corresponding to this modification</FONT> <BR><FONT color=#000000
size=2>>> (just a contribution).</FONT> <BR><FONT color=#000000
size=2>>> </FONT><BR><FONT color=#000000
size=2>>>>> Best regards</FONT> <BR><FONT color=#000000
size=2>>>>> Bruno</FONT> <BR><FONT color=#000000
size=2>>>>></FONT> <BR><FONT color=#000000
size=2>>>>></FONT> </P>
<P><FONT size=2>####</FONT> </P><BR><BR><BR>
<P> <B></B><B></B><B> <FONT
color=#000000 size=2>Christian Groves
<Christian.Groves@nteczone.com></FONT></B>
<UL>
<UL>
<UL>
<P><FONT color=#000000 size=2>08.05.2007
08:31 </FONT>
</P></UL></UL></UL>
<P> <FONT color=#000000
size=2>To: CHATRAS Bruno RD-CORE-ISS
<bruno.chatras@orange-ftgroup.com></FONT>
<BR> <FONT color=#000000
size=2>cc: "Wayne Cutler (CV/ETL)"
<wayne.cutler@ericsson.com>, Neal ZhuNing <zhuning@huawei.com>,
"Jerker Zetterlund (TN/EAB)" <jerker.zetterlund@ericsson.com>,
seppo.kauntola@nsn.com, Albrecht.Schwarz@alcatel-lucent.de,
CWaitzmann@alcatel-lucent.de, smaoui@nortel.com, Lin Yangbo
<linyangbo@huawei.com>, Tommy Young <tommy@huawei.com></FONT></P>
<P> <FONT color=#000000
size=2>Subject: Re: H.248 Ia Profile
Version 2 <BR></FONT></P><BR>
<UL>
<UL>
<UL>
<UL>
<P><FONT color=#000000 size=2>Hello Bruno, all,</FONT> </P>
<P><FONT color=#000000 size=2>With regards to linking Tispan releases
to profile versions I see that </FONT><BR><FONT color=#000000
size=2>adding optional elements to the profiles is the same as adding
then to </FONT><BR><FONT color=#000000 size=2>packages, the version
number is stepped. At least you then know the </FONT><BR><FONT
color=#000000 size=2>capabilities have changed and the new optional
features are available to </FONT><BR><FONT color=#000000 size=2>be
used.</FONT> </P>
<P><FONT color=#000000 size=2>On the IPDC issues based on your
response I've attached some proposed </FONT><BR><FONT color=#000000
size=2>marked up changes to ES283 018 (13bTD108r3). For me at least
the </FONT><BR><FONT color=#000000 size=2>distinction is where the MGC
knows the actual IPdomain its uses the IP </FONT><BR><FONT
color=#000000 size=2>realm identifier, where it doesn't its uses the
terminationId and lets </FONT><BR><FONT color=#000000 size=2>the MG
decide.</FONT> </P>
<P><FONT color=#000000 size=2>Other suggestions welcome.</FONT> </P>
<P><FONT color=#000000 size=2>Regards, Christian</FONT> </P>
<P><FONT color=#000000 size=2>CHATRAS Bruno RD-CORE-ISS wrote:</FONT>
<BR><FONT color=#000000 size=2>> Yes I want to contrinue using
implicit IP domain signalling. I want to be able to use new optional
features brought by TISPAN Release 2 while continuing to use the
existing mechanism for IP domain signalling. Actually I'm wondering
wheter it was not a mistake to assume from the beginning TISPAN
Release x maps to Profile Version x. It would certarinly be more
efficient to have several releases mapping to the same Profile version
with additional optional capabilties added over the
releases...</FONT></P>
<P><FONT color=#000000 size=2>></FONT> <BR><FONT color=#000000
size=2>> To answer your question, I think that the MGC does not
need to know the IP Domain nor the IP address pool. It just needs to
tell the MG on which "side" of the box the termination should be
created. It is then up to the MG to derive the IP Domain and
associated address pool to us.</FONT></P>
<P><FONT color=#000000 size=2>></FONT> <BR><FONT color=#000000
size=2>> Having said that, I still think that adding a mandatory
element to version N+1 of a protocol/profile means that versnion N+1
is not backward compatible with version N. </FONT></P>
<P><FONT color=#000000 size=2>></FONT> <BR><FONT color=#000000
size=2>> Best Regards</FONT> <BR><FONT color=#000000 size=2>>
Bruno</FONT> <BR><FONT color=#000000 size=2>></FONT> <BR><FONT
color=#000000 size=2>></FONT> <BR><FONT color=#000000 size=2>>
-----Message d'origine-----</FONT> <BR><FONT color=#000000 size=2>>
De : Christian Groves [</FONT><A
href="mailto:Christian.Groves@nteczone.com"><U></U><U><FONT
color=#0000ff
size=2>mailto:Christian.Groves@nteczone.com</FONT></U></A><FONT
color=#000000 size=2>] </FONT><BR><FONT color=#000000 size=2>>
Envoyé : lundi 30 avril 2007 07:33</FONT> <BR><FONT color=#000000
size=2>> À : Wayne Cutler (CV/ETL); CHATRAS Bruno
RD-CORE-ISS</FONT> <BR><FONT color=#000000 size=2>> Cc : Neal
ZhuNing; Jerker Zetterlund (TN/EAB); seppo.kauntola@nsn.com;
Albrecht.Schwarz@alcatel-lucent.de; CWaitzmann@alcatel-lucent.de;
smaoui@nortel.com; Lin Yangbo; Tommy Young</FONT></P>
<P><FONT color=#000000 size=2>> Objet : Re: H.248 Ia Profile
Version 2</FONT> <BR><FONT color=#000000 size=2>></FONT> <BR><FONT
color=#000000 size=2>> Hello all,</FONT> <BR><FONT color=#000000
size=2>></FONT> <BR><FONT color=#000000 size=2>> I don't agree
with the assertion that there is no need for compatibility between
version of profiles. I guess I'm old fashioned, to me a version change
is applied to a protocol whenever there is a change (as Wayne
suggests). As I've posted before H.248.1 sect 11.3 outlines rules for
up versioning the H.248 protocol. These rules have been/are applied to
up-versioning of packages and I don't see why they are not applicable
to</FONT></P>
<P><FONT color=#000000 size=2>> H.248 profile specifications. If
you want to make changes that aren't compatible then you can use a new
profile name. As Albrecht has suggested I will contribute to the next
Q.3/16 meeting on this. I also agree with Wayne's email I don't see
this change is a break of compatibility.</FONT></P>
<P><FONT color=#000000 size=2>></FONT> <BR><FONT color=#000000
size=2>> I do think this backwards compatibility issue is
distracting from the real issue however.</FONT> <BR><FONT
color=#000000 size=2>></FONT> <BR><FONT color=#000000 size=2>>
It seems to me Bruno's real issue is that he wants to continue to use
"implicit IP domain signalling" e.g. via the interface field in V2
without having to use H.248.41. Is this correct Bruno? If so then
before I make a proposal along those lines I have a question about
your comment:</FONT></P>
<P><FONT color=#000000 size=2>></FONT> <BR><FONT color=#000000
size=2>> /2/ If the IP realm identifier is
received by the BGF, it shall take</FONT> <BR><FONT color=#000000
size=2>> precedence over any IP realm that
may be derived from (or associated</FONT> <BR><FONT color=#000000
size=2>> to) the interface
identifier./</FONT> <BR><FONT color=#000000 size=2>></FONT>
<BR><FONT color=#000000 size=2>> In the case of Ia v1 where do you
see this association between the interfaceID and IP realm being set?
Does the MGC know which FQDN IP realm the termination will be
connected to when it requests an interface ID?, or is the IP realm
only known by the MG and may be assigned as a consequence of a request
for a particular interface?</FONT></P>
<P><FONT color=#000000 size=2>></FONT> <BR><FONT color=#000000
size=2>> Regards, Christian</FONT> <BR><FONT color=#000000
size=2>></FONT> <BR><FONT color=#000000 size=2>> PS: Just to be
clear when I talk about IP realm I mean a FQDN.</FONT> <BR><FONT
color=#000000 size=2>></FONT> <BR><FONT color=#000000 size=2>>
Wayne Cutler (CV/ETL) wrote:</FONT> <BR><FONT color=#000000
size=2>> </FONT><BR><FONT color=#000000 size=2>>>
Hi Bruno et al,</FONT> <BR><FONT color=#000000 size=2>>>
</FONT><BR><FONT color=#000000 size=2>>> I think that the fact
that we are stepping the version of Ia from 1 to</FONT> <BR><FONT
color=#000000 size=2>>> 2 means that something has changed -
else we would not step the </FONT><BR><FONT color=#000000
size=2>>> version. More specifically, I think that it means that
some additional </FONT><BR><FONT color=#000000 size=2>>>
mandatory fucntions have been added</FONT> <BR><FONT color=#000000
size=2>>> - and this translates in H248 as the addition of extra
mandatory </FONT><BR><FONT color=#000000 size=2>>>
packages.</FONT> <BR><FONT color=#000000 size=2>>>
</FONT><BR><FONT color=#000000 size=2>>> When a version is
stepped, the key point IMO is that no functionality </FONT><BR><FONT
color=#000000 size=2>>> is lost (i.e the upissued box can't be
less capable than its old </FONT><BR><FONT color=#000000
size=2>>> version). It is OK to add new functionality and also
be able to </FONT><BR><FONT color=#000000 size=2>>> realise
previous functionality in a different way. As long as this
</FONT><BR><FONT color=#000000 size=2>>> difference is clearly
described and understood, then this is not a </FONT><BR><FONT
color=#000000 size=2>>> problem. In this particular case, Ia v2
has added the new ipdc package </FONT><BR><FONT color=#000000
size=2>>> but also maintained the termination naming scheme from
Ia v1. So, I </FONT><BR><FONT color=#000000 size=2>>> don't
think there's a practical problem.</FONT> <BR><FONT color=#000000
size=2>>> </FONT><BR><FONT color=#000000 size=2>>>
Finally, given the way in which H248 allows a profile negotiation as
</FONT><BR><FONT color=#000000 size=2>>> part of its SC
procedures, I don't think there is a scenario where Ia</FONT>
<BR><FONT color=#000000 size=2>>> v2 needs to "interwork" with
Ia v1. </FONT><BR><FONT color=#000000 size=2>>>
</FONT><BR><FONT color=#000000 size=2>>> Regards, Wayne</FONT>
<BR><FONT color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>>
----------------------------------------------------------------------</FONT>
<BR><FONT color=#000000 size=2>>> --</FONT> <BR><FONT
color=#000000 size=2>>> *From:* CHATRAS Bruno RD-CORE-ISS</FONT>
<BR><FONT color=#000000 size=2>>> [</FONT><A
href="mailto:bruno.chatras@orange-ftgroup.com"><U></U><U><FONT
color=#0000ff
size=2>mailto:bruno.chatras@orange-ftgroup.com</FONT></U></A><FONT
color=#000000 size=2>]</FONT> <BR><FONT color=#000000 size=2>>>
*Sent:* 25 April 2007 09:52</FONT> <BR><FONT color=#000000
size=2>>> *To:* Neal ZhuNing; Jerker Zetterlund (TN/EAB)</FONT>
<BR><FONT color=#000000 size=2>>> *Cc:* seppo.kauntola@nsn.com;
Wayne Cutler (CV/ETL); </FONT><BR><FONT color=#000000 size=2>>>
Albrecht.Schwarz@alcatel-lucent.de; CWaitzmann@alcatel-lucent.de;
</FONT><BR><FONT color=#000000 size=2>>> smaoui@nortel.com;
Christian Groves; Lin Yangbo; Tommy Young</FONT> <BR><FONT
color=#000000 size=2>>> *Subject:* RE: H.248 Ia Profile Version
2</FONT> <BR><FONT color=#000000 size=2>>></FONT> <BR><FONT
color=#000000 size=2>>> Interesting... It's the first time I
read an explicit statement from </FONT><BR><FONT color=#000000
size=2>>> an ETSI member that interoperability between versions
of ETSI </FONT><BR><FONT color=#000000 size=2>>> standards is
unreasonable!!!</FONT> <BR><FONT color=#000000 size=2>>></FONT>
<BR><FONT color=#000000 size=2>>>
----------------------------------------------------------------------</FONT>
<BR><FONT color=#000000 size=2>>> -- *De :* Neal ZhuNing
[</FONT><A href="mailto:zhuning@huawei.com"><U></U><U><FONT
color=#0000ff size=2>mailto:zhuning@huawei.com</FONT></U></A><FONT
color=#000000 size=2>] *Envoyé :* mercredi</FONT> <BR><FONT
color=#000000 size=2>>> 25 avril 2007 10:47 *À :* 'Jerker
Zetterlund (TN/EAB)'; CHATRAS Bruno</FONT> <BR><FONT color=#000000
size=2>>> RD-CORE-ISS *Cc :* seppo.kauntola@nsn.com; 'Wayne
Cutler (CV/ETL)'; </FONT><BR><FONT color=#000000 size=2>>>
Albrecht.Schwarz@alcatel-lucent.de; CWaitzmann@alcatel-lucent.de;
</FONT><BR><FONT color=#000000 size=2>>> smaoui@nortel.com;
'Christian Groves'; 'Lin Yangbo'; 'Tommy Young'</FONT> <BR><FONT
color=#000000 size=2>>> *Objet :* RE: H.248 Ia Profile Version
2</FONT> <BR><FONT color=#000000 size=2>>></FONT> <BR><FONT
color=#000000 size=2>>> Hello Jerker and all,</FONT> <BR><FONT
color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>> I do agree with your viewpoint.
Profile version negotiation can </FONT><BR><FONT color=#000000
size=2>>> avoid backwards compatibility issue.
Interoperability between Ia /1 </FONT><BR><FONT color=#000000
size=2>>> and Ia/2 is unreasonable.</FONT> <BR><FONT
color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>> </FONT><BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>>
</FONT><BR><FONT color=#000000 size=2>>></FONT> <BR><FONT
color=#000000 size=2>>> BR</FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>>
Neal</FONT> <BR><FONT color=#000000 size=2>>></FONT> <BR><FONT
color=#000000 size=2>>>
----------------------------------------------------------------------</FONT>
<BR><FONT color=#000000 size=2>>> --</FONT> <BR><FONT
color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>> *From:* Jerker Zetterlund (TN/EAB)</FONT> <BR><FONT
color=#000000 size=2>>> [</FONT><A
href="mailto:jerker.zetterlund@ericsson.com"><U></U><U><FONT
color=#0000ff
size=2>mailto:jerker.zetterlund@ericsson.com</FONT></U></A><FONT
color=#000000 size=2>]</FONT> <BR><FONT color=#000000 size=2>>>
*Sent:* Wednesday, April 25, 2007 4:25 PM</FONT> <BR><FONT
color=#000000 size=2>>> *To:* Neal ZhuNing; CHATRAS Bruno
RD-CORE-ISS</FONT> <BR><FONT color=#000000 size=2>>> *Cc:*
seppo.kauntola@nsn.com; Wayne Cutler (CV/ETL); </FONT><BR><FONT
color=#000000 size=2>>> Albrecht.Schwarz@alcatel-lucent.de;
CWaitzmann@alcatel-lucent.de; </FONT><BR><FONT color=#000000
size=2>>> smaoui@nortel.com; Christian Groves; Lin Yangbo; Tommy
Young</FONT> <BR><FONT color=#000000 size=2>>> *Subject:* RE:
H.248 Ia Profile Version 2</FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>>
</FONT><BR><FONT color=#000000 size=2>>></FONT> <BR><FONT
color=#000000 size=2>>> Hello all,</FONT> <BR><FONT
color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>> </FONT><BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>> I think
this discussion is based on different understandings of the
</FONT><BR><FONT color=#000000 size=2>>> meaning of profile
version. In the drafting session of the March </FONT><BR><FONT
color=#000000 size=2>>> TISPAN meeting I think we assumed that
there is no need for direct </FONT><BR><FONT color=#000000
size=2>>> compatibility between v1 and v2 of the profie. If both
SPDF and MG </FONT><BR><FONT color=#000000 size=2>>> support Ia
v2 then this should not be a problem.</FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>>
</FONT><BR><FONT color=#000000 size=2>>></FONT> <BR><FONT
color=#000000 size=2>>> As I just wrote in the other email, my
personal view is that there is </FONT><BR><FONT color=#000000
size=2>>> no clear need for interoperability between Ia v1 and
Ia v2. As </FONT><BR><FONT color=#000000 size=2>>> profiles are
intended to limit the functionality to be used on an </FONT><BR><FONT
color=#000000 size=2>>> H.248 control association, then it seems
reasonable for the MG & MGC </FONT><BR><FONT color=#000000
size=2>>> to be able to be as precise as possible in which set
of functionality </FONT><BR><FONT color=#000000 size=2>>> to be
used.</FONT> <BR><FONT color=#000000 size=2>>></FONT> <BR><FONT
color=#000000 size=2>>> </FONT><BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>>
BR</FONT> <BR><FONT color=#000000 size=2>>></FONT> <BR><FONT
color=#000000 size=2>>> </FONT><BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>>
Jerker</FONT> <BR><FONT color=#000000 size=2>>></FONT> <BR><FONT
color=#000000 size=2>>> </FONT><BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>>
</FONT><BR><FONT color=#000000 size=2>>></FONT> <BR><FONT
color=#000000 size=2>>>
----------------------------------------------------------------------</FONT>
<BR><FONT color=#000000 size=2>>> --</FONT> <BR><FONT
color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>> *From:* Neal ZhuNing [</FONT><A
href="mailto:zhuning@huawei.com"><U></U><U><FONT color=#0000ff
size=2>mailto:zhuning@huawei.com</FONT></U></A><FONT color=#000000
size=2>]</FONT> <BR><FONT color=#000000 size=2>>> *Sent:* den 25
april 2007 09:21</FONT> <BR><FONT color=#000000 size=2>>> *To:*
'CHATRAS Bruno RD-CORE-ISS'</FONT> <BR><FONT color=#000000
size=2>>> *Cc:* seppo.kauntola@nsn.com; Wayne Cutler (CV/ETL);
</FONT><BR><FONT color=#000000 size=2>>>
Albrecht.Schwarz@alcatel-lucent.de; CWaitzmann@alcatel-lucent.de;
</FONT><BR><FONT color=#000000 size=2>>> Jerker Zetterlund
(TN/EAB); smaoui@nortel.com; 'Christian Groves'; </FONT><BR><FONT
color=#000000 size=2>>> 'Lin Yangbo'; 'Tommy Young'</FONT>
<BR><FONT color=#000000 size=2>>> *Subject:* RE: H.248 Ia
Profile Version 2</FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>> Hi
Bruno and all,</FONT> <BR><FONT color=#000000 size=2>>></FONT>
<BR><FONT color=#000000 size=2>>> Could we
discuss it to reach an agreement before meeting? (Not in</FONT>
<BR><FONT color=#000000 size=2>>> WG3 group)</FONT> <BR><FONT
color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>> Your second principle is hard to be
followed. when new ip </FONT><BR><FONT color=#000000 size=2>>>
termination is crreated, If the IP realm identifier indicates
</FONT><BR><FONT color=#000000 size=2>>> "IPDomain1",but the
terminationID in add request indicates an </FONT><BR><FONT
color=#000000 size=2>>> "interface" belongs to "IPDomain2" ,such
as "ip/9/9/$", How MG can do?</FONT> <BR><FONT color=#000000
size=2>>> Can MG change another interface identifier(such as
"ip/8/8/8" which </FONT><BR><FONT color=#000000 size=2>>>
belongs to ip domain "IPDomain1")in reply message ? i think it is not
</FONT><BR><FONT color=#000000 size=2>>> allowed by H.248
protocol. so if there is conflict brtween IP realm </FONT><BR><FONT
color=#000000 size=2>>> identifier and interface identifier, MG
should reply error . Is it </FONT><BR><FONT color=#000000
size=2>>> correct?</FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000
size=2>>> I agree that SPDF can choose
interface identifier according to IP </FONT><BR><FONT color=#000000
size=2>>> domain and send it to BGF. But , in most case ,It is
enough for SPDF </FONT><BR><FONT color=#000000 size=2>>> to only
send the IP realm identifier when the SPDF wishes to indicate
</FONT><BR><FONT color=#000000 size=2>>> the IP domain/realm of
the H.248 IP terminationin to BGF,such as in </FONT><BR><FONT
color=#000000 size=2>>> ADD request . do you agree this?</FONT>
<BR><FONT color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>> so I provide a principles list below:</FONT> <BR><FONT
color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>> 1)The IP realm identifier shall preferentially be used
if the SPDF </FONT><BR><FONT color=#000000 size=2>>> wishes to
indicate the IP domain/realm of the H.248 IP termination.</FONT>
<BR><FONT color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>> 2)If SPDF wishs to specify which physical or logical
interface a </FONT><BR><FONT color=#000000 size=2>>> termination
should be associated with in the MG, SPDF may set </FONT><BR><FONT
color=#000000 size=2>>> "interface" field. "interface" field may
be associated to IP realm.</FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>> 3)If
there is conflict between IP realm identifier and the ip domain
</FONT><BR><FONT color=#000000 size=2>>> the "interface"
field associated to ,error code should be replied.</FONT>
<BR><FONT color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>> </FONT><BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>>
BR</FONT> <BR><FONT color=#000000 size=2>>></FONT> <BR><FONT
color=#000000 size=2>>> Neal</FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>>
</FONT><BR><FONT color=#000000 size=2>>></FONT> <BR><FONT
color=#000000 size=2>>> -----Original Message-----</FONT>
<BR><FONT color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>> From: CHATRAS Bruno RD-CORE-ISS </FONT><BR><FONT
color=#000000 size=2>>> [</FONT><A
href="mailto:bruno.chatras@ORANGE-FTGROUP.COM"><U></U><U><FONT
color=#0000ff
size=2>mailto:bruno.chatras@ORANGE-FTGROUP.COM</FONT></U></A><FONT
color=#000000 size=2>]</FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>> Sent:
Tuesday, April 24, 2007 8:42 PM</FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>> To:
TISPAN_WG3@LIST.ETSI.ORG</FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>>
Subject: Re: H.248 Ia Profile Version 2</FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>>
</FONT><BR><FONT color=#000000 size=2>>></FONT> <BR><FONT
color=#000000 size=2>>> OK then I disagree with 5.1.4.2.15.1 and
will submit a CR against it. </FONT><BR><FONT color=#000000
size=2>>> Let's talk about his at the meeting. Note that a
"version 1" BGF is </FONT><BR><FONT color=#000000 size=2>>> able
to derive the IP domain (and tehrefore the address ppol from
</FONT><BR><FONT color=#000000 size=2>>> which the termination
address shall be taken) from the "interface"</FONT> <BR><FONT
color=#000000 size=2>>> field. Release 2 shall not disallow this
behavior. Therefore I think </FONT><BR><FONT color=#000000
size=2>>> that we should draft a text along the following
principles:</FONT> <BR><FONT color=#000000 size=2>>></FONT>
<BR><FONT color=#000000 size=2>>> </FONT><BR><FONT
color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>> 1/ The IP realm identifier shall be sent to the BGF
when the SPDF </FONT><BR><FONT color=#000000 size=2>>> wishes to
indicate explictly the IP domain/realm of the H.248 IP
</FONT><BR><FONT color=#000000 size=2>>> termination.</FONT>
<BR><FONT color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>> </FONT><BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>> 2/ If
the IP realm identifier is received by the BGF, it shall take
</FONT><BR><FONT color=#000000 size=2>>> precedence over any IP
realm that may be derived from (or associated</FONT> <BR><FONT
color=#000000 size=2>>> to) the interface identifier.</FONT>
<BR><FONT color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>> </FONT><BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>>
BC</FONT> <BR><FONT color=#000000 size=2>>></FONT> <BR><FONT
color=#000000 size=2>>> </FONT><BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>>
</FONT><BR><FONT color=#000000 size=2>>></FONT> <BR><FONT
color=#000000 size=2>>> This behavior</FONT> <BR><FONT
color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>> </FONT><BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>>
-----Message d'origine-----</FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>> De :
Neal ZhuNing [</FONT><A
href="mailto:zhuning@huawei.com"><U></U><U><FONT color=#0000ff
size=2>mailto:zhuning@huawei.com</FONT></U></A><FONT color=#000000
size=2>]</FONT> <BR><FONT color=#000000 size=2>>></FONT>
<BR><FONT color=#000000 size=2>>> Envoyé : mardi 24 avril 2007
12:59</FONT> <BR><FONT color=#000000 size=2>>></FONT> <BR><FONT
color=#000000 size=2>>> À : CHATRAS Bruno RD-CORE-ISS;
TISPAN_WG3@LIST.ETSI.ORG</FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>> Objet :
RE: H.248 Ia Profile Version 2</FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>>
</FONT><BR><FONT color=#000000 size=2>>></FONT> <BR><FONT
color=#000000 size=2>>> Hi Bruno,</FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>> In the
latest draft, Session 5.14.2.15.1:</FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>> "The
ephemeral termination string layout</FONT> <BR><FONT color=#000000
size=2>>> ("ip/<group>/<interface>/<id>") may
still be used to specify which </FONT><BR><FONT color=#000000
size=2>>> physical or logical interface a termination should be
associated with </FONT><BR><FONT color=#000000 size=2>>> in the
MG. but the "interface" field shall not be used for IP
</FONT><BR><FONT color=#000000 size=2>>> realm/domain indication
."</FONT> <BR><FONT color=#000000 size=2>>></FONT> <BR><FONT
color=#000000 size=2>>> </FONT><BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>> The
"interface" field shall not be used for IP realm/domain
</FONT><BR><FONT color=#000000 size=2>>> indication, so if SPDF
wishes to indicate the IP domain/realm of the</FONT> <BR><FONT
color=#000000 size=2>>> H.248 IP termination, only ipdc property
can be used in ia/2.</FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>>
</FONT><BR><FONT color=#000000 size=2>>></FONT> <BR><FONT
color=#000000 size=2>>> BR</FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>>
Neal</FONT> <BR><FONT color=#000000 size=2>>></FONT> <BR><FONT
color=#000000 size=2>>> </FONT><BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>>
</FONT><BR><FONT color=#000000 size=2>>></FONT> <BR><FONT
color=#000000 size=2>>> -----Original Message-----</FONT>
<BR><FONT color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>> From: CHATRAS Bruno RD-CORE-ISS </FONT><BR><FONT
color=#000000 size=2>>> [</FONT><A
href="mailto:bruno.chatras@orange-ftgroup.com"><U></U><U><FONT
color=#0000ff
size=2>mailto:bruno.chatras@orange-ftgroup.com</FONT></U></A><FONT
color=#000000 size=2>]</FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>> Sent:
Tuesday, April 24, 2007 6:48 PM</FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>> To:
Neal ZhuNing; TISPAN_WG3@LIST.ETSI.ORG</FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>>
Subject: RE: H.248 Ia Profile Version 2</FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>>
</FONT><BR><FONT color=#000000 size=2>>></FONT> <BR><FONT
color=#000000 size=2>>> Based on operator's policy and BGF
capabilities (e.g. if the IP domain </FONT><BR><FONT color=#000000
size=2>>> can't be derived from the interface id by the
BGF).</FONT> <BR><FONT color=#000000 size=2>>></FONT> <BR><FONT
color=#000000 size=2>>> </FONT><BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>>
-----Message d'origine-----</FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>> De :
Neal ZhuNing [</FONT><A
href="mailto:zhuning@huawei.com"><U></U><U><FONT color=#0000ff
size=2>mailto:zhuning@huawei.com</FONT></U></A><FONT color=#000000
size=2>] Envoyé : mardi 24 avril</FONT> <BR><FONT color=#000000
size=2>>> 2007 12:44 À : CHATRAS Bruno RD-CORE-ISS;
TISPAN_WG3@LIST.ETSI.ORG</FONT> <BR><FONT color=#000000
size=2>>> Objet : RE: H.248 Ia Profile Version 2</FONT>
<BR><FONT color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>> </FONT><BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>> Hi
Bruno,</FONT> <BR><FONT color=#000000 size=2>>></FONT> <BR><FONT
color=#000000 size=2>>> In which condition the SPDF
wishes to indicate explictly the IP </FONT><BR><FONT color=#000000
size=2>>> domain/realm of the H.248 IP termination??</FONT>
<BR><FONT color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>> </FONT><BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>>
BR</FONT> <BR><FONT color=#000000 size=2>>></FONT> <BR><FONT
color=#000000 size=2>>> Neal</FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>>
</FONT><BR><FONT color=#000000 size=2>>></FONT> <BR><FONT
color=#000000 size=2>>> -----Original Message-----</FONT>
<BR><FONT color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>> From: CHATRAS Bruno RD-CORE-ISS </FONT><BR><FONT
color=#000000 size=2>>> [</FONT><A
href="mailto:bruno.chatras@orange-ftgroup.com"><U></U><U><FONT
color=#0000ff
size=2>mailto:bruno.chatras@orange-ftgroup.com</FONT></U></A><FONT
color=#000000 size=2>]</FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>> Sent:
Tuesday, April 24, 2007 6:40 PM</FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>> To:
Neal ZhuNing; TISPAN_WG3@LIST.ETSI.ORG</FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>>
Subject: RE: H.248 Ia Profile Version 2</FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>>
</FONT><BR><FONT color=#000000 size=2>>></FONT> <BR><FONT
color=#000000 size=2>>> I would prefer</FONT> <BR><FONT
color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>> </FONT><BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>>
"The IP realm identifier shall be sent to the BGF when the SPDF
</FONT><BR><FONT color=#000000 size=2>>> wishes to indicate
explictly the IP domain/realm of the H.248 IP </FONT><BR><FONT
color=#000000 size=2>>> termination."</FONT> <BR><FONT
color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>> </FONT><BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>>
-----Message d'origine-----</FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>> De :
Neal ZhuNing [</FONT><A
href="mailto:zhuning@HUAWEI.COM"><U></U><U><FONT color=#0000ff
size=2>mailto:zhuning@HUAWEI.COM</FONT></U></A><FONT color=#000000
size=2>] Envoyé : mardi 24 avril</FONT> <BR><FONT color=#000000
size=2>>> 2007</FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>> 12:37 À
: TISPAN_WG3@LIST.ETSI.ORG Objet : Re: H.248 Ia Profile</FONT>
<BR><FONT color=#000000 size=2>>> Version 2</FONT> <BR><FONT
color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>> </FONT><BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>> Hi
Bruno,</FONT> <BR><FONT color=#000000 size=2>>></FONT> <BR><FONT
color=#000000 size=2>>> </FONT><BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>> What
about: "The IP realm identifier shall be sent to the BGF in order
</FONT><BR><FONT color=#000000 size=2>>> to indicate the IP
domain/realm of the H.248 IP termination."</FONT> <BR><FONT
color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>> </FONT><BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>> Your
state "if explicit signalling of the IP domain/realm of the H.248
</FONT><BR><FONT color=#000000 size=2>>> IP termination is
required." is unclear. In which condition this </FONT><BR><FONT
color=#000000 size=2>>> explicit signaling is required? I think
this condition is that SPDF </FONT><BR><FONT color=#000000
size=2>>> wants to indicate the IP domain/realm of the H.248 IP
termination.</FONT> <BR><FONT color=#000000 size=2>>></FONT>
<BR><FONT color=#000000 size=2>>> </FONT><BR><FONT
color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>> </FONT><BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>>
BR</FONT> <BR><FONT color=#000000 size=2>>></FONT> <BR><FONT
color=#000000 size=2>>> Neal</FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>>
</FONT><BR><FONT color=#000000 size=2>>></FONT> <BR><FONT
color=#000000 size=2>>> -----Original Message-----</FONT>
<BR><FONT color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>> From: CHATRAS Bruno RD-CORE-ISS </FONT><BR><FONT
color=#000000 size=2>>> [</FONT><A
href="mailto:bruno.chatras@orange-ftgroup.com"><U></U><U><FONT
color=#0000ff
size=2>mailto:bruno.chatras@orange-ftgroup.com</FONT></U></A><FONT
color=#000000 size=2>]</FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>> Sent:
Tuesday, April 24, 2007 6:28 PM</FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>> To:
Neal ZhuNing; TISPAN_WG3@LIST.ETSI.ORG</FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>>
Subject: RE: H.248 Ia Profile Version 2</FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>>
</FONT><BR><FONT color=#000000 size=2>>></FONT> <BR><FONT
color=#000000 size=2>>> Use of "MUST" in ETSI documents is not
recommended by the ETSI </FONT><BR><FONT color=#000000 size=2>>>
Drafting Rules anyway... (See Clause 23 of the ETSI Drafting
Rules).</FONT> <BR><FONT color=#000000 size=2>>></FONT>
<BR><FONT color=#000000 size=2>>> </FONT><BR><FONT
color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>> What about: "The IP realm identifier shall be sent to
the BGF if </FONT><BR><FONT color=#000000 size=2>>> explicit
signalling of the IP domain/realm of the H.248 IP termination
</FONT><BR><FONT color=#000000 size=2>>> is required."</FONT>
<BR><FONT color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>> </FONT><BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>>
</FONT><BR><FONT color=#000000 size=2>>></FONT> <BR><FONT
color=#000000 size=2>>> Bruno</FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>>
</FONT><BR><FONT color=#000000 size=2>>></FONT> <BR><FONT
color=#000000 size=2>>> -----Message d'origine-----</FONT>
<BR><FONT color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>> De : Neal ZhuNing [</FONT><A
href="mailto:zhuning@huawei.com"><U></U><U><FONT color=#0000ff
size=2>mailto:zhuning@huawei.com</FONT></U></A><FONT color=#000000
size=2>] Envoyé : mardi 24 avril</FONT> <BR><FONT color=#000000
size=2>>> 2007</FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>> 12:04 À
: CHATRAS Bruno RD-CORE-ISS; TISPAN_WG3@LIST.ETSI.ORG Objet :
RE:</FONT> <BR><FONT color=#000000 size=2>>></FONT> <BR><FONT
color=#000000 size=2>>> H.248 Ia Profile Version 2</FONT>
<BR><FONT color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>> </FONT><BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>> Hi
Bruno,</FONT> <BR><FONT color=#000000 size=2>>></FONT> <BR><FONT
color=#000000 size=2>>> It should be "MUST",
not "MAY".</FONT> <BR><FONT color=#000000 size=2>>></FONT>
<BR><FONT color=#000000 size=2>>> When SPDF
wants to indicate the IP domain/realm of the H.248 IP </FONT><BR><FONT
color=#000000 size=2>>> termination, the ipdc property MUST be
sent to the BGF.</FONT> <BR><FONT color=#000000 size=2>>></FONT>
<BR><FONT color=#000000 size=2>>> If there is
no ipdc property in the message, it is still a valid </FONT><BR><FONT
color=#000000 size=2>>> message, but it can not indicate the IP
domain/realm. BGF creates IP </FONT><BR><FONT color=#000000
size=2>>> terminations on the special "interface "according to
the (ALL or</FONT> <BR><FONT color=#000000 size=2>>> partial)
wildcard terminationID.</FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>>
</FONT><BR><FONT color=#000000 size=2>>></FONT> <BR><FONT
color=#000000 size=2>>> BR</FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>>
Neal</FONT> <BR><FONT color=#000000 size=2>>></FONT> <BR><FONT
color=#000000 size=2>>> </FONT><BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>>
-----Original Message-----</FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>> From:
CHATRAS Bruno RD-CORE-ISS </FONT><BR><FONT color=#000000
size=2>>> [</FONT><A
href="mailto:bruno.chatras@orange-ftgroup.com"><U></U><U><FONT
color=#0000ff
size=2>mailto:bruno.chatras@orange-ftgroup.com</FONT></U></A><FONT
color=#000000 size=2>]</FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>> Sent:
Tuesday, April 24, 2007 5:49 PM</FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>> To:
Neal ZhuNing; TISPAN_WG3@LIST.ETSI.ORG</FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>>
Subject: RE: H.248 Ia Profile Version 2</FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>>
</FONT><BR><FONT color=#000000 size=2>>></FONT> <BR><FONT
color=#000000 size=2>>> Yes I was referring to this text</FONT>
<BR><FONT color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>> </FONT><BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>> "The IP
realm identifier must be sent to the BGF in order to indicate
</FONT><BR><FONT color=#000000 size=2>>> the IP domain/realm of
the H.248 IP termination."</FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>>
</FONT><BR><FONT color=#000000 size=2>>></FONT> <BR><FONT
color=#000000 size=2>>> Would you agree to replace "MUST" with
"MAY"?</FONT> <BR><FONT color=#000000 size=2>>></FONT> <BR><FONT
color=#000000 size=2>>> </FONT><BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>> Best
Regards</FONT> <BR><FONT color=#000000 size=2>>></FONT>
<BR><FONT color=#000000 size=2>>> Bruno</FONT> <BR><FONT
color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>> </FONT><BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>>
-----Message d'origine-----</FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>> De :
Neal ZhuNing [</FONT><A
href="mailto:zhuning@huawei.com"><U></U><U><FONT color=#0000ff
size=2>mailto:zhuning@huawei.com</FONT></U></A><FONT color=#000000
size=2>] Envoyé : mardi 24 avril</FONT> <BR><FONT color=#000000
size=2>>> 2007</FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>> 11:27 À
: CHATRAS Bruno RD-CORE-ISS; TISPAN_WG3@LIST.ETSI.ORG Objet :
RE:</FONT> <BR><FONT color=#000000 size=2>>></FONT> <BR><FONT
color=#000000 size=2>>> H.248 Ia Profile Version 2</FONT>
<BR><FONT color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>> </FONT><BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>> Hi
Bruno,</FONT> <BR><FONT color=#000000 size=2>>></FONT> <BR><FONT
color=#000000 size=2>>> </FONT><BR><FONT
color=#000000 size=2>>>> I have seen that somewhere in the
text of the Latest Draft it is</FONT> <BR><FONT color=#000000
size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>> stated</FONT>
<BR><FONT color=#000000
size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>> that >the MGC SHALL
set the H.248.41 property. Unless there is an </FONT><BR><FONT
color=#000000 size=2>>> error in the text, >this seems to
assume interpretation "b".</FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>>
</FONT><BR><FONT color=#000000 size=2>>></FONT> <BR><FONT
color=#000000 size=2>>> I can not find your this state in the
text of the latest draft, maybe </FONT><BR><FONT color=#000000
size=2>>> what you refer to is Ia/2 session 5.14.2.15.1
??</FONT> <BR><FONT color=#000000 size=2>>></FONT> <BR><FONT
color=#000000 size=2>>> </FONT><BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>> Best
Regards,</FONT> <BR><FONT color=#000000 size=2>>></FONT>
<BR><FONT color=#000000 size=2>>> Neal</FONT> <BR><FONT
color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>> </FONT><BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>>
</FONT><BR><FONT color=#000000 size=2>>></FONT> <BR><FONT
color=#000000 size=2>>> -----Original Message-----</FONT>
<BR><FONT color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>> From: CHATRAS Bruno RD-CORE-ISS </FONT><BR><FONT
color=#000000 size=2>>> [</FONT><A
href="mailto:bruno.chatras@ORANGE-FTGROUP.COM"><U></U><U><FONT
color=#0000ff
size=2>mailto:bruno.chatras@ORANGE-FTGROUP.COM</FONT></U></A><FONT
color=#000000 size=2>]</FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>> Sent:
Tuesday, April 24, 2007 3:27 PM</FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>> To:
TISPAN_WG3@LIST.ETSI.ORG</FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>>
Subject: Re: H.248 Ia Profile Version 2</FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>>
</FONT><BR><FONT color=#000000 size=2>>></FONT> <BR><FONT
color=#000000 size=2>>> Carsten,</FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>>
</FONT><BR><FONT color=#000000 size=2>>></FONT> <BR><FONT
color=#000000 size=2>>> I agree that there would not be any
compatibility issue with </FONT><BR><FONT color=#000000
size=2>>> interpretation "a". However, I have seen that
somewhere in the text of </FONT><BR><FONT color=#000000
size=2>>> the Latest Draft it is stated that the MGC SHALL set
the H.248.41 </FONT><BR><FONT color=#000000 size=2>>> property.
Unless there is an error in the text, this seems to assume
</FONT><BR><FONT color=#000000 size=2>>> interpretation
"b".</FONT> <BR><FONT color=#000000 size=2>>></FONT> <BR><FONT
color=#000000 size=2>>> </FONT><BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>> Best
Regards</FONT> <BR><FONT color=#000000 size=2>>></FONT>
<BR><FONT color=#000000 size=2>>> Bruno</FONT> <BR><FONT
color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>> </FONT><BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>>
-----Message d'origine-----</FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>> De :
Carsten Waitzmann [</FONT><A
href="mailto:cwaitzmann@ALCATEL-LUCENT.DE"><U></U><U><FONT
color=#0000ff
size=2>mailto:cwaitzmann@ALCATEL-LUCENT.DE</FONT></U></A><FONT
color=#000000 size=2>]</FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>> Envoyé
: mardi 24 avril 2007 09:21</FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>> À :
TISPAN_WG3@LIST.ETSI.ORG</FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>> Objet :
Re: H.248 Ia Profile Version 2</FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>>
</FONT><BR><FONT color=#000000 size=2>>></FONT> <BR><FONT
color=#000000 size=2>>> Hello Bruno,</FONT> <BR><FONT
color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>> </FONT><BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>> Related
to your understanding of backward compatibility:</FONT> <BR><FONT
color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>> > My understanding is that backward
compatibility in the work item > </FONT><BR><FONT
color=#000000 size=2>>> description was intended to refer to the
ability for version n+1 to > </FONT><BR><FONT color=#000000
size=2>>> understand version n without requiring version
negotiation to occur > </FONT><BR><FONT color=#000000
size=2>>> before.</FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>>
</FONT><BR><FONT color=#000000 size=2>>></FONT> <BR><FONT
color=#000000 size=2>>> I'd like to ask the following
question:</FONT> <BR><FONT color=#000000 size=2>>></FONT>
<BR><FONT color=#000000 size=2>>> What does "mandatory package"
within a H.248 profile mean:</FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>> a) it
just means that a MG/MGC announcing compliance to this profile
</FONT><BR><FONT color=#000000 size=2>>> can expected to have
implemented all these packages (and therefore all </FONT><BR><FONT
color=#000000 size=2>>> received</FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>> H.248
messages using any property, signal, etc. of these packages is
</FONT><BR><FONT color=#000000 size=2>>> properly understood and
processed). However it doesn't imply that the </FONT><BR><FONT
color=#000000 size=2>>> packages have to be always used whenever
possible.</FONT> <BR><FONT color=#000000 size=2>>></FONT>
<BR><FONT color=#000000 size=2>>> b) same as a) but mandatory
packages have to be always used whenever </FONT><BR><FONT
color=#000000 size=2>>> possible.</FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>>
</FONT><BR><FONT color=#000000 size=2>>></FONT> <BR><FONT
color=#000000 size=2>>> If it is a), then I don't think that
there is a backward compatibility </FONT><BR><FONT color=#000000
size=2>>> issue. In the specific case of H.248.41, for example
an MGC may still </FONT><BR><FONT color=#000000 size=2>>> run v1
w/o .41 and the MG although running v2, may perfectly receive
</FONT><BR><FONT color=#000000 size=2>>> and process the
message. v2 remains backward compatible, as the v1 </FONT><BR><FONT
color=#000000 size=2>>> capability to indicate a
physical/logical interface within the IP </FONT><BR><FONT
color=#000000 size=2>>> termination string is still available.
It wouldn't be backward </FONT><BR><FONT color=#000000 size=2>>>
compatible if the v2 profile would have changed the semantic of
</FONT><BR><FONT color=#000000 size=2>>> "interface" within the
IP termination string.</FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>>
</FONT><BR><FONT color=#000000 size=2>>></FONT> <BR><FONT
color=#000000 size=2>>> best regards</FONT> <BR><FONT
color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>> Carsten</FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>>
</FONT><BR><FONT color=#000000 size=2>>></FONT> <BR><FONT
color=#000000 size=2>>> Albrecht Schwarz wrote:</FONT> <BR><FONT
color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>> </FONT><BR><FONT color=#000000
size=2>>>> Bruno</FONT> <BR><FONT color=#000000
size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>>> My
understanding is that backward compatibility in the work item</FONT>
<BR><FONT color=#000000
size=2>>>>>
</FONT><BR><FONT color=#000000 size=2>>>> description was
intended to refer to the ability</FONT> <BR><FONT color=#000000
size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>>> for version n+1
to understand version n without requiring version</FONT> <BR><FONT
color=#000000
size=2>>>>>
</FONT><BR><FONT color=#000000 size=2>>>> negotiation to
occur before. This is usually what</FONT> <BR><FONT color=#000000
size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>>> is meant in
other ITU-T and ETSI standards dealing with signalling.</FONT>
<BR><FONT color=#000000
size=2>>>>>
</FONT><BR><FONT color=#000000 size=2>>>> Couldn't find any
appropriate definition for "backward compatibility"</FONT> <BR><FONT
color=#000000 size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>> in ITU-T & ETSI
(like the one for codecs from H.262).</FONT> <BR><FONT color=#000000
size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>> There are
signalling protocols with and without a version </FONT><BR><FONT
color=#000000 size=2>>>> negotiation</FONT> <BR><FONT
color=#000000 size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>> mechanism. The
understanding of "backward compatibility" might be</FONT> <BR><FONT
color=#000000 size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>> slightly different
for both categories. Guess the protocols without </FONT><BR><FONT
color=#000000 size=2>>>> a</FONT> <BR><FONT color=#000000
size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>> version negotiation
method are the majority like the capability set</FONT> <BR><FONT
color=#000000 size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>> based ITU-T
protocols like e.g. INAP, BICC or Q.2630.x.</FONT> <BR><FONT
color=#000000 size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>> H.248 belongs to
the category with an</FONT> <BR><FONT color=#000000
size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>> a) integral
mechanism for protocol version negotiation and in </FONT><BR><FONT
color=#000000 size=2>>>> addition</FONT> <BR><FONT
color=#000000 size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>> a</FONT> <BR><FONT
color=#000000 size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>> b) mechanism for
profile negotiation</FONT> <BR><FONT color=#000000
size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>> and also</FONT>
<BR><FONT color=#000000
size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>> c) a multi profile
mode capability (H.248.18).</FONT> <BR><FONT color=#000000
size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>> The used protocol
capabilities are related to the lifetime of the</FONT> <BR><FONT
color=#000000 size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>> H.248 Control
Association (CA), starting the negotiation at CA</FONT> <BR><FONT
color=#000000 size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>> establishment.</FONT>
<BR><FONT color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>> </FONT><BR><FONT color=#000000
size=2>>>> Capability upgrade procedures may lead to a re-new
or </FONT><BR><FONT color=#000000 size=2>>>>
re-establishment</FONT> <BR><FONT color=#000000
size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>> of the CA.</FONT>
<BR><FONT color=#000000
size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>> A definition for
"backward compatibility" for H.248 CAs might</FONT> <BR><FONT
color=#000000 size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>> therefore different
to other protocols without such mechanisms.</FONT> <BR><FONT
color=#000000 size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>> We got four WIs for
H.248 Profiles, - a MG registration with the</FONT> <BR><FONT
color=#000000 size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>> correspondent
ProfileID is part of a profile specification.</FONT> <BR><FONT
color=#000000 size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>> Saying that, the
meaning of backward compatibility in the WI</FONT> <BR><FONT
color=#000000 size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>> description means
that the MG registers with Ia/2 in my opinion.</FONT> <BR><FONT
color=#000000 size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>> In case of a
fallback requirement to Ia/1, then current draft my be</FONT>
<BR><FONT color=#000000
size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>> extended for
H.248.18 support (but this requires a contribution).</FONT> <BR><FONT
color=#000000 size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>> Albrecht</FONT>
<BR><FONT color=#000000
size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>> </FONT><BR><FONT
color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>> </FONT><BR><FONT color=#000000
size=2>>>>
Christian Groves</FONT> <BR><FONT color=#000000
size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>> </FONT><BR><FONT
color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>> </FONT><BR><FONT color=#000000
size=2>>>>
<Christian.Groves@NT
To:</FONT> <BR><FONT color=#000000
size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>
TISPAN_WG3@LIST.ETSI.ORG</FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>>
</FONT><BR><FONT color=#000000 size=2>>></FONT> <BR><FONT
color=#000000 size=2>>> </FONT><BR><FONT
color=#000000
size=2>>>>
ECZONE.COM>
cc:</FONT> <BR><FONT color=#000000
size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>> </FONT><BR><FONT
color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>> </FONT><BR><FONT color=#000000
size=2>>>>
Subject: Re: </FONT><BR><FONT color=#000000 size=2>>>>
H.248</FONT> <BR><FONT color=#000000
size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>> Ia</FONT> <BR><FONT
color=#000000 size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>> Profile Version
2
</FONT><BR><FONT color=#000000 size=2>>></FONT> <BR><FONT
color=#000000 size=2>>> </FONT><BR><FONT
color=#000000
size=2>>>>
23.04.2007 09:55</FONT> <BR><FONT color=#000000
size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>> </FONT><BR><FONT
color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>> </FONT><BR><FONT color=#000000
size=2>>>>
Please respond to</FONT> <BR><FONT color=#000000
size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>> </FONT><BR><FONT
color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>> </FONT><BR><FONT color=#000000
size=2>>>>
Christian Groves</FONT> <BR><FONT color=#000000
size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>> </FONT><BR><FONT
color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>> </FONT><BR><FONT color=#000000
size=2>>> </FONT><BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000
size=2>>> </FONT><BR><FONT color=#000000
size=2>>>> Hello Bruno,</FONT> <BR><FONT color=#000000
size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>> What does "ability
for version n+1 to understand version n" mean? </FONT><BR><FONT
color=#000000 size=2>>>> Even</FONT> <BR><FONT color=#000000
size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>> in the scenario we
are talking about a MG with a version n+1 control</FONT> <BR><FONT
color=#000000 size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>> association will
understand the version n message because the </FONT><BR><FONT
color=#000000 size=2>>>> encoding</FONT> <BR><FONT
color=#000000 size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>> has not changed
(thus backwards compatible by the definition below)</FONT> <BR><FONT
color=#000000 size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>> but it will reject
it because of new required functionality. </FONT><BR><FONT
color=#000000 size=2>>>> Likewise</FONT> <BR><FONT
color=#000000 size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>> it seems that
"before version negotiation" has been prompted by the</FONT> <BR><FONT
color=#000000 size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>> email discussion.
For some, such mechanisms are integral for</FONT> <BR><FONT
color=#000000 size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>> compatibility
mechanisms.</FONT> <BR><FONT color=#000000
size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>> Do you have a
reference to a general description of "backwards</FONT> <BR><FONT
color=#000000 size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>>
compatibility"? The term is used alot but I don't know any
description</FONT> <BR><FONT color=#000000
size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>> other than that in
H.248.1. For example H.248.1 section 11.3</FONT> <BR><FONT
color=#000000 size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>> Negotiation of
Protocol Version offers rules for new versions. ie.</FONT> <BR><FONT
color=#000000 size=2>>>>
</FONT><BR><FONT color=#000000
size=2>>>> /When extending the
protocol with new versions, the following </FONT><BR><FONT
color=#000000 size=2>>>> rules</FONT> <BR><FONT color=#000000
size=2>>>>
</FONT><BR><FONT color=#000000
size=2>>>> should be
followed:/</FONT> <BR><FONT color=#000000
size=2>>>>
</FONT><BR><FONT color=#000000
size=2>>>> /1) Existing protocol
elements, i.e., procedures, parameters,</FONT> <BR><FONT color=#000000
size=2>>>>
</FONT><BR><FONT color=#000000
size=2>>>> descriptor, property,
values, should/</FONT> <BR><FONT color=#000000
size=2>>>>
</FONT><BR><FONT color=#000000
size=2>>>> /not be changed unless a
protocol error needs to be corrected or </FONT><BR><FONT color=#000000
size=2>>>> it</FONT> <BR><FONT color=#000000
size=2>>>>
</FONT><BR><FONT color=#000000
size=2>>>> becomes necessary
to/</FONT> <BR><FONT color=#000000
size=2>>>>
</FONT><BR><FONT color=#000000
size=2>>>> /change the operation of
the service that is being supported by </FONT><BR><FONT color=#000000
size=2>>>> the</FONT> <BR><FONT color=#000000
size=2>>>>
</FONT><BR><FONT color=#000000
size=2>>>> protocol./</FONT>
<BR><FONT color=#000000
size=2>>>>
</FONT><BR><FONT color=#000000
size=2>>>> /2) The semantics of a
command, a parameter, a descriptor, a</FONT> <BR><FONT color=#000000
size=2>>>>
</FONT><BR><FONT color=#000000
size=2>>>> property, or a value
should not be/</FONT> <BR><FONT color=#000000
size=2>>>>
</FONT><BR><FONT color=#000000
size=2>>>> /changed./</FONT>
<BR><FONT color=#000000
size=2>>>>
</FONT><BR><FONT color=#000000
size=2>>>> /3) Established rules for
formatting and encoding messages and</FONT> <BR><FONT color=#000000
size=2>>>>
</FONT><BR><FONT color=#000000
size=2>>>> parameters should not
be/</FONT> <BR><FONT color=#000000
size=2>>>>
</FONT><BR><FONT color=#000000
size=2>>>> /modified./</FONT>
<BR><FONT color=#000000
size=2>>>>
</FONT><BR><FONT color=#000000
size=2>>>> /4) When information
elements are found to be obsolete they can </FONT><BR><FONT
color=#000000 size=2>>>> be</FONT> <BR><FONT color=#000000
size=2>>>>
</FONT><BR><FONT color=#000000
size=2>>>> marked as not
used./</FONT> <BR><FONT color=#000000
size=2>>>>
</FONT><BR><FONT color=#000000
size=2>>>> /However, the identifier
for that information element will be </FONT><BR><FONT color=#000000
size=2>>>> marked</FONT> <BR><FONT color=#000000
size=2>>>>
</FONT><BR><FONT color=#000000
size=2>>>> as reserved. In that
way/</FONT> <BR><FONT color=#000000
size=2>>>>
</FONT><BR><FONT color=#000000
size=2>>>> /it cannot be used in
future versions./</FONT> <BR><FONT color=#000000
size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>> These rules were
adopted to ensure backwards compatibility. I think</FONT> <BR><FONT
color=#000000 size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>> these rules are
equally applicable to the case of profiles. When the</FONT> <BR><FONT
color=#000000 size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>> MGC and MG agree on
the use of a control association they agree on </FONT><BR><FONT
color=#000000 size=2>>>> the</FONT> <BR><FONT color=#000000
size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>> H.248.1 version and
the profile (including version).</FONT> <BR><FONT color=#000000
size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>> Regards,
Christian</FONT> <BR><FONT color=#000000
size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>> CHATRAS Bruno
RD-CORE-ISS wrote:</FONT> <BR><FONT color=#000000
size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>>> Hello
Chirstian,</FONT> <BR><FONT color=#000000
size=2>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>> My
understanding is that backward compatibility in the work item</FONT>
<BR><FONT color=#000000
size=2>>>>>
</FONT><BR><FONT color=#000000 size=2>>>> description was
intended to refer to the ability for version n+1 to</FONT> <BR><FONT
color=#000000 size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>> understand version
n without requiring version negotiation to occur</FONT> <BR><FONT
color=#000000 size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>> before.</FONT>
<BR><FONT color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>> </FONT><BR><FONT color=#000000
size=2>>>> This is usually what is meant in other ITU-T and
ETSI standards</FONT> <BR><FONT color=#000000
size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>> dealing with
signalling.</FONT> <BR><FONT color=#000000
size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>>> Best
Regards,</FONT> <BR><FONT color=#000000
size=2>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>> Bruno</FONT>
<BR><FONT color=#000000
size=2>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>> -----Message
d'origine-----</FONT> <BR><FONT color=#000000
size=2>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>> De : Christian
Groves [</FONT><A
href="mailto:Christian.Groves@NTECZONE.COM"><U></U><U><FONT
color=#0000ff
size=2>mailto:Christian.Groves@NTECZONE.COM</FONT></U></A><FONT
color=#000000 size=2>]</FONT> <BR><FONT color=#000000
size=2>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>> Envoyé : lundi
23 avril 2007 02:58</FONT> <BR><FONT color=#000000
size=2>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>> À :
TISPAN_WG3@LIST.ETSI.ORG</FONT> <BR><FONT color=#000000
size=2>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>> Objet : Re:
H.248 Ia Profile Version 2</FONT> <BR><FONT color=#000000
size=2>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>> Hello
Bruno,</FONT> <BR><FONT color=#000000
size=2>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>> What was the
definition of "backward compatibility" that the work</FONT> <BR><FONT
color=#000000
size=2>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>> item</FONT>
<BR><FONT color=#000000
size=2>>>>>
</FONT><BR><FONT color=#000000 size=2>>>> description
assumed? It seems that people have different interpretations.</FONT>
<BR><FONT color=#000000
size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>>> Regards,
Christian</FONT> <BR><FONT color=#000000
size=2>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>> CHATRAS Bruno
RD-CORE-ISS wrote:</FONT> <BR><FONT color=#000000
size=2>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>> This is
version negotiation, not backward compatibility.... Both</FONT>
<BR><FONT color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>> approaches are
valid protocol design approaches and have their pros</FONT> <BR><FONT
color=#000000 size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>> and cons. However,
the Work Item description assumed "backward</FONT> <BR><FONT
color=#000000 size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>> compatibility
between version 1 and 2...</FONT> <BR><FONT color=#000000
size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>>
-----Message d'origine-----</FONT> <BR><FONT color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>> De : Neal
ZhuNing [</FONT><A href="mailto:zhuning@HUAWEI.COM"><U></U><U><FONT
color=#0000ff size=2>mailto:zhuning@HUAWEI.COM</FONT></U></A><FONT
color=#000000 size=2>] Envoyé : vendredi 20</FONT> <BR><FONT
color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>> avril 2007
04:09 À : TISPAN_WG3@LIST.ETSI.ORG Objet : Re: H.248 Ia</FONT>
<BR><FONT color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>> Profile
Version 2</FONT> <BR><FONT color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000
size=2>>>>>> Agree Albrecht's
state.</FONT> <BR><FONT color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000
size=2>>>>>> When a BGF
registers with a ProfileID "ETSI_BGF/1" 0r</FONT> <BR><FONT
color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>>
"ETSI_BGF/2",</FONT> <BR><FONT color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>> corresponding ia
profile(ia/2 or ia/1) should be applied.</FONT> <BR><FONT
color=#000000 size=2>>>>
</FONT><BR><FONT color=#000000
size=2>>>>>> I think the
Profile-based backward compatibility between ia/2 </FONT><BR><FONT
color=#000000 size=2>>>>>> and</FONT> <BR><FONT
color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>> ia/1 is based on
their functions. Ia/2 can realize all the functions</FONT> <BR><FONT
color=#000000 size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>> of Ia/1, but new
better methods can be used, even it is mandatory.</FONT> <BR><FONT
color=#000000 size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>> BR</FONT>
<BR><FONT color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>> Neal</FONT>
<BR><FONT color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>>
-----Original Message-----</FONT> <BR><FONT color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>> From:
Albrecht Schwarz [</FONT><A
href="mailto:Albrecht.Schwarz@ALCATEL-LUCENT.DE"><U></U><U><FONT
color=#0000ff
size=2>mailto:Albrecht.Schwarz@ALCATEL-LUCENT.DE</FONT></U></A><FONT
color=#000000 size=2>]</FONT> <BR><FONT color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>> Sent:
Thursday, April 19, 2007 6:50 PM</FONT> <BR><FONT color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>> To:
TISPAN_WG3@LIST.ETSI.ORG</FONT> <BR><FONT color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>> Subject:
Re: H.248 Ia Profile Version 2</FONT> <BR><FONT color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>> [Sorry for
using your initials as abbreviation BC for backward</FONT> <BR><FONT
color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>>
compatibility :-)]</FONT> <BR><FONT color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>> I do agree
to your statement.</FONT> <BR><FONT color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>> Important
here is the "scope of the protocol" in my understanding.</FONT>
<BR><FONT color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>> There would
be a compatibility issue when the SPDF & BGF would</FONT>
<BR><FONT color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>>
operate</FONT> <BR><FONT color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>> Ia interface in the
"NoProfile" mode, i.e. the BGF would not include</FONT> <BR><FONT
color=#000000 size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>> the
ServiceChangeProfile parameter for registration.</FONT> <BR><FONT
color=#000000 size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>> But the
protocol scope is limited when registering with a </FONT><BR><FONT
color=#000000 size=2>>>>>> ProfileID</FONT> <BR><FONT
color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>> (as</FONT>
<BR><FONT color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>> in case of ES 283
018). There are then only "ETSI_BGF/1" or "ETSI_BGF/2"</FONT>
<BR><FONT color=#000000
size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>> H.248
Messages between a single SPDF-BGF tandem.</FONT> <BR><FONT
color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>> I think
that this is the crucial point concerning "protcol scope"</FONT>
<BR><FONT color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>> for</FONT>
<BR><FONT color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>>
H.248</FONT> <BR><FONT color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>> interface:
"Profile-less" vs "Profile-based" operated H.248 </FONT><BR><FONT
color=#000000 size=2>>>>>> Control</FONT> <BR><FONT
color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>
Associations.</FONT> <BR><FONT color=#000000
size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>>
Albrecht</FONT> <BR><FONT color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000
size=2>>>>>>
"CHATRAS Bruno</FONT> <BR><FONT color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000
size=2>>>>>>
RD-CORE-ISS"
To: "Neal</FONT> <BR><FONT color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>> ZhuNing"
<zhuning@huawei.com>, </FONT><BR><FONT color=#000000
size=2>>>>>>
<Albrecht.Schwarz@ALCATEL-LUCENT.DE></FONT> <BR><FONT
color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000
size=2>>>>>>
<bruno.chatras@orange-f
cc:</FONT> <BR><FONT color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>>
<TISPAN_WG3@LIST.ETSI.ORG></FONT> <BR><FONT color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000
size=2>>>>>>
tgroup.com>
Subject: RE: </FONT><BR><FONT color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>> H.248</FONT> <BR><FONT
color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>> </FONT><BR><FONT color=#000000
size=2>>>> Ia</FONT> <BR><FONT color=#000000
size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>> Profile
Version 2</FONT> <BR><FONT color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000
size=2>>>>>>
19.04.2007 12:28</FONT> <BR><FONT color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>> Adding a
mandatory parameter to version n+1 of a protocol means
</FONT><BR><FONT color=#000000 size=2>>>>>> that</FONT>
<BR><FONT color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>> a</FONT>
<BR><FONT color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>> message conforming
to the version n of this protocol is not a valid</FONT> <BR><FONT
color=#000000 size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>> message for an
implementation conforming to version n+1 of this</FONT> <BR><FONT
color=#000000 size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>> protocol. Is not
this a compatobility issue?</FONT> <BR><FONT color=#000000
size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>> BC</FONT>
<BR><FONT color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>>
-----Message d'origine-----</FONT> <BR><FONT color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>> De : Neal
ZhuNing [</FONT><A href="mailto:zhuning@huawei.com"><U></U><U><FONT
color=#0000ff size=2>mailto:zhuning@huawei.com</FONT></U></A><FONT
color=#000000 size=2>] Envoyé : jeudi 19</FONT> <BR><FONT
color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>>
avril</FONT> <BR><FONT color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>> 2007 11:55
À : Albrecht.Schwarz@ALCATEL-LUCENT.DE; CHATRAS Bruno</FONT> <BR><FONT
color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>> RD-CORE-ISS
Cc : TISPAN_WG3@LIST.ETSI.ORG Objet : RE: H.248 Ia</FONT> <BR><FONT
color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>> Profile
Version 2</FONT> <BR><FONT color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>> Hi
Albrecht, Bruno,</FONT> <BR><FONT color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000
size=2>>>>>> In Ia/1, the
hierarchical termination name does not </FONT><BR><FONT color=#000000
size=2>>>>>> specifically</FONT> <BR><FONT
color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>> mention that it is
used to identify the IP domain that a termination</FONT> <BR><FONT
color=#000000 size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>> is connected to,
nor does it give an example of the syntax </FONT><BR><FONT
color=#000000 size=2>>>> associated</FONT> <BR><FONT
color=#000000 size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>> with the
"interface". So maybe there is no backward compatibility on</FONT>
<BR><FONT color=#000000
size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>> this</FONT>
<BR><FONT color=#000000
size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>> issue.</FONT> <BR><FONT
color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>> </FONT><BR><FONT color=#000000
size=2>>>>>> In Ia/2, the hierarchical
termination name may still be used to</FONT> <BR><FONT color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>> specify which
physical or logical interface a termination should be</FONT> <BR><FONT
color=#000000 size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>> associated with in
the MG.</FONT> <BR><FONT color=#000000
size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>> So, the
hierarchical termination name mechanism is same in Ia/1
</FONT><BR><FONT color=#000000 size=2>>>>>> and</FONT>
<BR><FONT color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>> Ia/2, there is no
backward compatibility problem.</FONT> <BR><FONT color=#000000
size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>> BR</FONT>
<BR><FONT color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>> Neal</FONT>
<BR><FONT color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>>
-----Original Message-----</FONT> <BR><FONT color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>> From:
Albrecht Schwarz [</FONT><A
href="mailto:Albrecht.Schwarz@ALCATEL-LUCENT.DE"><U></U><U><FONT
color=#0000ff
size=2>mailto:Albrecht.Schwarz@ALCATEL-LUCENT.DE</FONT></U></A><FONT
color=#000000 size=2>]</FONT> <BR><FONT color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>> Sent:
Thursday, April 19, 2007 5:21 PM</FONT> <BR><FONT color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>> To:
TISPAN_WG3@LIST.ETSI.ORG</FONT> <BR><FONT color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>> Subject:
Re: H.248 Ia Profile Version 2</FONT> <BR><FONT color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>>
Bruno,</FONT> <BR><FONT color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>> when we
discussed this, we couldn't see a violation of the </FONT><BR><FONT
color=#000000 size=2>>>>>> backward</FONT> <BR><FONT
color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>> compatibility (BC)
principle.</FONT> <BR><FONT color=#000000
size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>> The MG is
registering either with Ia/1 or Ia/2, but not with both</FONT>
<BR><FONT color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>> profile versions
(like in a multiple profile mode), the used IP</FONT> <BR><FONT
color=#000000 size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>> realm/domain
indication mechanism is unambiguous.</FONT> <BR><FONT color=#000000
size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>> The profile
principle is thus supporting BC targets.</FONT> <BR><FONT
color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>> A single
H.248 Control Association is either operated with Ia/1 or</FONT>
<BR><FONT color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>> Ia/2.</FONT> <BR><FONT
color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>> </FONT><BR><FONT color=#000000
size=2>>>>>> Do I overlook sth?</FONT> <BR><FONT
color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>>
Albrecht</FONT> <BR><FONT color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>> PS</FONT>
<BR><FONT color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>> Above
principle is/may also used for other "capability upgrades",</FONT>
<BR><FONT color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>> like
H.248.10 replacement by H.248.11 in a next profile version,
</FONT><BR><FONT color=#000000 size=2>>>>>> etc</FONT>
<BR><FONT color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>> etc</FONT>
<BR><FONT color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000
size=2>>>>>>
CHATRAS Bruno</FONT> <BR><FONT color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000
size=2>>>>>>
RD-CORE-ISS
To:</FONT> <BR><FONT color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>>
TISPAN_WG3@LIST.ETSI.ORG</FONT> <BR><FONT color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000
size=2>>>>>>
<bruno.chatras@ORANGE-F
cc:</FONT> <BR><FONT color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000
size=2>>>>>>
TGROUP.COM>
Subject: H.248 Ia</FONT> <BR><FONT color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>> Profile
Version 2</FONT> <BR><FONT color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000
size=2>>>>>>
19.04.2007 11:12</FONT> <BR><FONT color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000
size=2>>>>>>
Please respond to</FONT> <BR><FONT color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000
size=2>>>>>>
CHATRAS Bruno</FONT> <BR><FONT color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000
size=2>>>>>>
RD-CORE-ISS</FONT> <BR><FONT color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>> Ray,
Wayne,</FONT> <BR><FONT color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>> I just had
a look to the Latest Draft of WI03098 (Ia profile </FONT><BR><FONT
color=#000000 size=2>>>>>> Release</FONT> <BR><FONT
color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>> 2)</FONT>
<BR><FONT color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>> and saw that
support of the new IPDC package is mandatory rather </FONT><BR><FONT
color=#000000 size=2>>>> than</FONT> <BR><FONT color=#000000
size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>> optional.</FONT>
<BR><FONT color=#000000
size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>> This
contradicts the Work Item description which says explictly
</FONT><BR><FONT color=#000000 size=2>>>>>> that</FONT>
<BR><FONT color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>> "The Ia profile
version 2 shall maintain backwards compatibility </FONT><BR><FONT
color=#000000 size=2>>>> with</FONT> <BR><FONT color=#000000
size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>> version 1."
The meeting reports says that adding the IPDC package </FONT><BR><FONT
color=#000000 size=2>>>> was</FONT> <BR><FONT color=#000000
size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>> indeed agreed but
does not say whether it should be mandatory or</FONT> <BR><FONT
color=#000000 size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>> optional.</FONT>
<BR><FONT color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>> </FONT><BR><FONT color=#000000
size=2>>>> I believe that we should either make this package
optional or made </FONT><BR><FONT color=#000000 size=2>>>>
an</FONT> <BR><FONT color=#000000
size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>> attempt to modify
the Work Item description. I assume we can't </FONT><BR><FONT
color=#000000 size=2>>>> approve</FONT> <BR><FONT
color=#000000 size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>> a deliverable which
explicitly contradicts a Work Item description.</FONT> <BR><FONT
color=#000000 size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>> BTW, what
is the procedure for TB approval of this modification.</FONT>
<BR><FONT color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>>
There</FONT> <BR><FONT color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>> does not seem to be
any CR corresponding to this modification (just </FONT><BR><FONT
color=#000000 size=2>>>> a</FONT> <BR><FONT color=#000000
size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>>
contribution).</FONT> <BR><FONT color=#000000
size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>> Best
regards</FONT> <BR><FONT color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>>
Bruno</FONT> <BR><FONT color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000
size=2>>>>>> Mail archive
for TISPAN_WG3 can be browsed at the following url :</FONT> <BR><FONT
color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000
size=2>>>>>>
</FONT><A href="http://list.etsi.org/TISPAN_WG3.html"><U></U><U><FONT
color=#0000ff
size=2>http://list.etsi.org/TISPAN_WG3.html</FONT></U></A> <BR><FONT
color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>>
------------------------------------------------------------------</FONT>
<BR><FONT color=#000000 size=2>>>>>> -</FONT> <BR><FONT
color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>> Mail
archive for TISPAN_WG3 can be browsed at the following url
:</FONT> <BR><FONT color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000
size=2>>>>>>
</FONT><A href="http://list.etsi.org/TISPAN_WG3.html"><U></U><U><FONT
color=#0000ff
size=2>http://list.etsi.org/TISPAN_WG3.html</FONT></U></A> <BR><FONT
color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>>
------------------------------------------------------------------</FONT>
<BR><FONT color=#000000 size=2>>>>>> -</FONT> <BR><FONT
color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>>
------------------------------------------------------------------</FONT>
<BR><FONT color=#000000 size=2>>>>>> -</FONT> <BR><FONT
color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>> Mail
archive for TISPAN_WG3 can be browsed at the following url
:</FONT> <BR><FONT color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000
size=2>>>>>>
</FONT><A href="http://list.etsi.org/TISPAN_WG3.html"><U></U><U><FONT
color=#0000ff
size=2>http://list.etsi.org/TISPAN_WG3.html</FONT></U></A> <BR><FONT
color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>>
------------------------------------------------------------------</FONT>
<BR><FONT color=#000000 size=2>>>>>> -</FONT> <BR><FONT
color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>>
------------------------------------------------------------------</FONT>
<BR><FONT color=#000000 size=2>>>>>> -</FONT> <BR><FONT
color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>> Mail
archive for TISPAN_WG3 can be browsed at the following url
:</FONT> <BR><FONT color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000
size=2>>>>>>
</FONT><A href="http://list.etsi.org/TISPAN_WG3.html"><U></U><U><FONT
color=#0000ff
size=2>http://list.etsi.org/TISPAN_WG3.html</FONT></U></A> <BR><FONT
color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>>
------------------------------------------------------------------</FONT>
<BR><FONT color=#000000 size=2>>>>>> -</FONT> <BR><FONT
color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>>
------------------------------------------------------------------</FONT>
<BR><FONT color=#000000 size=2>>>>>> -</FONT> <BR><FONT
color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>> Mail
archive for TISPAN_WG3 can be browsed at the following url
:</FONT> <BR><FONT color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000
size=2>>>>>>
</FONT><A href="http://list.etsi.org/TISPAN_WG3.html"><U></U><U><FONT
color=#0000ff
size=2>http://list.etsi.org/TISPAN_WG3.html</FONT></U></A> <BR><FONT
color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>>
------------------------------------------------------------------</FONT>
<BR><FONT color=#000000 size=2>>>>>> -</FONT> <BR><FONT
color=#000000
size=2>>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>
-------------------------------------------------------------------</FONT>
<BR><FONT color=#000000
size=2>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>> Mail archive
for TISPAN_WG3 can be browsed at the following url :</FONT>
<BR><FONT color=#000000
size=2>>>>>
</FONT><BR><FONT color=#000000
size=2>>>>>
</FONT><A href="http://list.etsi.org/TISPAN_WG3.html"><U></U><U><FONT
color=#0000ff
size=2>http://list.etsi.org/TISPAN_WG3.html</FONT></U></A> <BR><FONT
color=#000000
size=2>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>>
-------------------------------------------------------------------</FONT>
<BR><FONT color=#000000
size=2>>>>>
</FONT><BR><FONT color=#000000 size=2>>>>
-------------------------------------------------------------------</FONT>
<BR><FONT color=#000000
size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>> Mail archive for
TISPAN_WG3 can be browsed at the following url :</FONT>
<BR><FONT color=#000000
size=2>>>>
</FONT><BR><FONT color=#000000
size=2>>>>
</FONT><A href="http://list.etsi.org/TISPAN_WG3.html"><U></U><U><FONT
color=#0000ff
size=2>http://list.etsi.org/TISPAN_WG3.html</FONT></U></A> <BR><FONT
color=#000000 size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>>
-------------------------------------------------------------------</FONT>
<BR><FONT color=#000000
size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>>
-------------------------------------------------------------------</FONT>
<BR><FONT color=#000000
size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>> Mail archive for
TISPAN_WG3 can be browsed at the following url :</FONT>
<BR><FONT color=#000000
size=2>>>>
</FONT><BR><FONT color=#000000
size=2>>>>
</FONT><A href="http://list.etsi.org/TISPAN_WG3.html"><U></U><U><FONT
color=#0000ff
size=2>http://list.etsi.org/TISPAN_WG3.html</FONT></U></A> <BR><FONT
color=#000000 size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>>>
-------------------------------------------------------------------</FONT>
<BR><FONT color=#000000
size=2>>>>
</FONT><BR><FONT color=#000000 size=2>>> </FONT><BR><FONT
color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>> </FONT><BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>>
--</FONT> <BR><FONT color=#000000 size=2>>></FONT> <BR><FONT
color=#000000 size=2>>> Alcatel-Lucent Deutschland AG</FONT>
<BR><FONT color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>> Sitz der Gesellschaft: Stuttgart - Amtsgericht
Stuttgart HRB 4026 </FONT><BR><FONT color=#000000 size=2>>>
Vorsitzender des Aufsichtsrats: Michael Oppenhoff</FONT> <BR><FONT
color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>> Vorstand: Wolfgang Weik (Vors.), Dr. Rainer Fechner,
Juergen </FONT><BR><FONT color=#000000 size=2>>> Poesinger, Alf
Henryk Wulf</FONT> <BR><FONT color=#000000 size=2>>></FONT>
<BR><FONT color=#000000 size=2>>> </FONT><BR><FONT
color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>>
-------------------------------------------------------------------</FONT>
<BR><FONT color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>> Mail archive for TISPAN_WG3 can be browsed at
the following url :</FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000
size=2>>>
</FONT><A href="http://list.etsi.org/TISPAN_WG3.html"><U></U><U><FONT
color=#0000ff
size=2>http://list.etsi.org/TISPAN_WG3.html</FONT></U></A> <BR><FONT
color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>>
-------------------------------------------------------------------</FONT>
<BR><FONT color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>> </FONT><BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>>
-------------------------------------------------------------------</FONT>
<BR><FONT color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>> Mail archive for TISPAN_WG3 can be browsed at
the following url :</FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000
size=2>>>
</FONT><A href="http://list.etsi.org/TISPAN_WG3.html"><U></U><U><FONT
color=#0000ff
size=2>http://list.etsi.org/TISPAN_WG3.html</FONT></U></A> <BR><FONT
color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>>
-------------------------------------------------------------------</FONT>
<BR><FONT color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>> </FONT><BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>>
-------------------------------------------------------------------</FONT>
<BR><FONT color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>> Mail archive for TISPAN_WG3 can be browsed at
the following url :</FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000
size=2>>>
</FONT><A href="http://list.etsi.org/TISPAN_WG3.html"><U></U><U><FONT
color=#0000ff
size=2>http://list.etsi.org/TISPAN_WG3.html</FONT></U></A> <BR><FONT
color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>>
-------------------------------------------------------------------</FONT>
<BR><FONT color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>> </FONT><BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000 size=2>>>
-------------------------------------------------------------------</FONT>
<BR><FONT color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>> Mail archive for TISPAN_WG3 can be browsed at
the following url :</FONT> <BR><FONT color=#000000
size=2>>></FONT> <BR><FONT color=#000000
size=2>>>
</FONT><A href="http://list.etsi.org/TISPAN_WG3.html"><U></U><U><FONT
color=#0000ff
size=2>http://list.etsi.org/TISPAN_WG3.html</FONT></U></A> <BR><FONT
color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>>
-------------------------------------------------------------------</FONT>
<BR><FONT color=#000000 size=2>>></FONT> <BR><FONT color=#000000
size=2>>> </FONT><BR><FONT color=#000000
size=2>></FONT> <BR><FONT color=#000000 size=2>></FONT>
<BR><FONT color=#000000 size=2>>
</FONT></P></UL></UL></UL></UL>
<P><FONT color=#000000 size=2>[attachment "iprealm_update.doc" deleted by
Albrecht SCHWARZ/DE/ALCATEL]</FONT> </P></BLOCKQUOTE></BODY></HTML>