
From snemana@sonusnet.com  Mon Jan 14 06:16:10 2013
Return-Path: <snemana@sonusnet.com>
X-Original-To: sigtran@ietfa.amsl.com
Delivered-To: sigtran@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1470821F888E for <sigtran@ietfa.amsl.com>; Mon, 14 Jan 2013 06:16:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2o3FyBRIm+mm for <sigtran@ietfa.amsl.com>; Mon, 14 Jan 2013 06:16:09 -0800 (PST)
Received: from na3sys010aog111.obsmtp.com (na3sys010aog111.obsmtp.com [74.125.245.90]) by ietfa.amsl.com (Postfix) with ESMTP id 4DE9A21F8844 for <sigtran@ietf.org>; Mon, 14 Jan 2013 06:16:09 -0800 (PST)
Received: from USMA-EX-HUB2.sonusnet.com ([69.147.176.212]) (using TLSv1) by na3sys010aob111.postini.com ([74.125.244.12]) with SMTP ID DSNKUPQTKJwbOojcqDPhzLTwOpXhQYvqeSoq@postini.com; Mon, 14 Jan 2013 06:16:09 PST
Received: from USMA-EX-MB2.sonusnet.com ([fe80::c51d:eb9c:bce7:e4b0]) by USMA-EX-HUB2.sonusnet.com ([2002:42cb:5a11::42cb:5a11]) with mapi id 14.02.0318.004; Mon, 14 Jan 2013 09:16:07 -0500
From: "Nemana, Satya" <snemana@sonusnet.com>
To: "sigtran@ietf.org" <sigtran@ietf.org>
Thread-Topic: Encoding scheme, Number of Digits parameters, GTI in SUA message
Thread-Index: Ac3yYYjWOvEXd6SwSg6dUrmRexeG0g==
Date: Mon, 14 Jan 2013 14:16:06 +0000
Message-ID: <A4C75474DC72BC44A5517224ED0604C51359DE@USMA-EX-MB2.sonusnet.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.128.99.157]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [Sigtran] Encoding scheme, Number of Digits parameters, GTI in SUA message
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Signaling Transport <sigtran.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sigtran>, <mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sigtran>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sigtran>, <mailto:sigtran-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jan 2013 14:16:10 -0000

Hello!

I had two questions trying to understand a problem with GT in SUA.

1) Why is the encoding scheme parameter normally present in the SS7 message=
s absent in the SUA message as a parameter. In the absence of the encoding =
scheme in the SUA Called party GT, how does the SUA NIF analyze the digits.

2) The number of digits in the SUA message (called party) is already known =
depending on the digits included, i.e if I have a GT of 0123456789, then I =
have 10 digits. In such a situation where the number of digits present is i=
mplicitly known, why do we have an other parameter " Number of Digits" to t=
ell the same? What is the significance of this parameter?
In most cases, GT is a phone number, why would we want to use only part of =
it for processing the message? (there would have been a wildcard GT provisi=
oned for the destination(s) on the SG/STP to handle the case of using a sub=
set of the digits.

3) Also, in section 3.10.2.3, the text
<snip>
0001 Nature of Address is taken over
<snip>
What does "taken over" mean? (Sorry, I don't mean the English meaning of it=
 but taken over in this sentence : When there is an explicit Nature of Addr=
ess parameter in SUA messages , I don't understand what is taken over here?=
)

4) ANSI specs and ITU specs for message format for different GTI values are=
 different
Example :
ANSI GTI 1 : Global title includes translation type, numbering plan and enc=
oding scheme
ITU GTI 1 : global title includes nature of address indicator only
SUA RFC only specifies ITU spec Q.713 reference.
Is it just for an example, and that similar formats should be used from ANS=
I or other specs wherever possible?
Or is it to say that the format for the particular GTI is now redefined wit=
h the SUA spec and this should be used?

Regards,
Satya

From bidulock@openss7.org  Tue Jan 15 13:42:09 2013
Return-Path: <bidulock@openss7.org>
X-Original-To: sigtran@ietfa.amsl.com
Delivered-To: sigtran@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D468521F84E3 for <sigtran@ietfa.amsl.com>; Tue, 15 Jan 2013 13:42:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rnsfEhEVOjfz for <sigtran@ietfa.amsl.com>; Tue, 15 Jan 2013 13:42:09 -0800 (PST)
Received: from gw.openss7.com (gw.openss7.com [142.59.210.7]) by ietfa.amsl.com (Postfix) with ESMTP id E641621F84E0 for <sigtran@ietf.org>; Tue, 15 Jan 2013 13:42:08 -0800 (PST)
Received: from wilbur.pigworks.openss7.net (ns5.evil.openss7.net [192.168.9.5]) by gw.openss7.com (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id r0FLg2BS016729; Tue, 15 Jan 2013 14:42:03 -0700
Received: from wilbur.pigworks.openss7.net (localhost [127.0.0.1]) by wilbur.pigworks.openss7.net (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id r0FLg2jR020181; Tue, 15 Jan 2013 14:42:02 -0700
Received: (from brian@localhost) by wilbur.pigworks.openss7.net (8.14.3/8.14.3/Submit) id r0FLg1Qw020180; Tue, 15 Jan 2013 14:42:01 -0700
Date: Tue, 15 Jan 2013 14:42:01 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Nemana, Satya" <snemana@sonusnet.com>
Message-ID: <20130115214201.GA17314@openss7.org>
Mail-Followup-To: "Nemana, Satya" <snemana@sonusnet.com>, "sigtran@ietf.org" <sigtran@ietf.org>
References: <A4C75474DC72BC44A5517224ED0604C51359DE@USMA-EX-MB2.sonusnet.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <A4C75474DC72BC44A5517224ED0604C51359DE@USMA-EX-MB2.sonusnet.com>
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
X-Spam-To: <blockme@openss7.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: "sigtran@ietf.org" <sigtran@ietf.org>
Subject: Re: [Sigtran] Encoding scheme, Number of Digits parameters, GTI in	SUA message
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: bidulock@openss7.org
List-Id: Signaling Transport <sigtran.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sigtran>, <mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sigtran>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sigtran>, <mailto:sigtran-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Jan 2013 21:42:09 -0000

Satya,

Please see comments inline...

Nemana, Satya wrote:                    (Mon, 14 Jan 2013 14:16:06)
> Hello!
> 
> I had two questions trying to understand a problem with GT in SUA.
> 
> 1) Why is the encoding scheme parameter normally present in the SS7
> messages absent in the SUA message as a parameter. In the absence of
> the encoding scheme in the SUA Called party GT, how does the SUA NIF
> analyze the digits.

They are always encoded as digits (i.e. nibble encoded digits) per
RFC 3868/3.10.2.3.

> 2) The number of digits in the SUA message (called party) is already
> known depending on the digits included, i.e if I have a GT of
> 0123456789, then I have 10 digits. In such a situation where the
> number of digits present is implicitly known, why do we have an other
> parameter " Number of Digits" to tell the same? What is the
> significance of this parameter?

10 digits is not implicitly known unless it can be determined from the
translation type.  5 octets of digits can be either 9 or 10 digits.  The
odd/even indicator indicates this in SS7.  In SUA we used a full digit
count (we had enough bits) instead of an odd/even indicator.  It avoids
having to interpret fillers and can be directly calculated off of the
odd/even indicator and the length of the digits (in octets).

> In most cases, GT is a phone number, why would we want to use only
> part of it for processing the message? (there would have been a
> wildcard GT provisioned for the destination(s) on the SG/STP to handle
> the case of using a subset of the digits.

The no. digits field does not encode a subset of the GT digits.  For
example, 5 octets of digits with a 'no. digits' field of 3 would be an
error: the field would have to be 9 or 10.

> 3) Also, in section 3.10.2.3, the text
> <snip>
> 0001 Nature of Address is taken over
> <snip>
> What does "taken over" mean? (Sorry, I don't mean the English meaning
> of it but taken over in this sentence : When there is an explicit
> Nature of Address parameter in SUA messages , I don't understand what
> is taken over here?)

It assumes the same value at the corresponding field in the SS7 SCCP
message: that is, it is "taken over" from the SS7 message.

> 4) ANSI specs and ITU specs for message format for different GTI
> values are different
>
> Example :
> ANSI GTI 1 : Global title includes translation type, numbering plan
> and encoding scheme
> ITU GTI 1 : global title includes nature of address indicator only
> SUA RFC only specifies ITU spec Q.713 reference.
> Is it just for an example, and that similar formats should be used
> from ANSI or other specs wherever possible?
> Or is it to say that the format for the particular GTI is now
> redefined with the SUA spec and this should be used?

Read the line over the descripton of GTI values:

  "GTI (Global Title Indicator, defined in chapter 3.4.2.3 of Q.713)"

These _are_ the values of the ITU GTI.   ANSI defines fewer and more
restricted GTIs.  SUA uses the ITU GTIs and maps ANSI values into them.
ANSI GTI(1) maps into ITU GTI(3), ANSI GTI(2) maps into ITU GIT(2).

I hope that helps.

--brian

-- 
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/

From snemana@sonusnet.com  Wed Jan 16 09:06:09 2013
Return-Path: <snemana@sonusnet.com>
X-Original-To: sigtran@ietfa.amsl.com
Delivered-To: sigtran@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 92BA921F8B67 for <sigtran@ietfa.amsl.com>; Wed, 16 Jan 2013 09:06:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b3RF9h2sEyMj for <sigtran@ietfa.amsl.com>; Wed, 16 Jan 2013 09:06:08 -0800 (PST)
Received: from na3sys010aog105.obsmtp.com (na3sys010aog105.obsmtp.com [74.125.245.78]) by ietfa.amsl.com (Postfix) with ESMTP id 84BCA21F8941 for <sigtran@ietf.org>; Wed, 16 Jan 2013 09:06:08 -0800 (PST)
Received: from usma-ex-hub1.sonusnet.com ([69.147.176.212]) (using TLSv1) by na3sys010aob105.postini.com ([74.125.244.12]) with SMTP ID DSNKUPbeAGgywyWEsiVGnPFlE7RnsNscmKkX@postini.com; Wed, 16 Jan 2013 09:06:08 PST
Received: from USMA-EX-MB2.sonusnet.com ([fe80::c51d:eb9c:bce7:e4b0]) by usma-ex-hub1.sonusnet.com ([2002:42cb:5a10::42cb:5a10]) with mapi id 14.02.0318.004; Wed, 16 Jan 2013 12:06:06 -0500
From: "Nemana, Satya" <snemana@sonusnet.com>
To: "bidulock@openss7.org" <bidulock@openss7.org>
Thread-Topic: [Sigtran] Encoding scheme, Number of Digits parameters, GTI in SUA message
Thread-Index: AQHN82ksZCNGGpE7VUC6fTaoFVXAEJhMLvxg
Date: Wed, 16 Jan 2013 17:06:05 +0000
Message-ID: <A4C75474DC72BC44A5517224ED0604C51372C4@USMA-EX-MB2.sonusnet.com>
References: <A4C75474DC72BC44A5517224ED0604C51359DE@USMA-EX-MB2.sonusnet.com> <20130115214201.GA17314@openss7.org>
In-Reply-To: <20130115214201.GA17314@openss7.org>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.128.99.157]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "sigtran@ietf.org" <sigtran@ietf.org>
Subject: Re: [Sigtran] Encoding scheme, Number of Digits parameters, GTI in	SUA message
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Signaling Transport <sigtran.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sigtran>, <mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sigtran>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sigtran>, <mailto:sigtran-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Jan 2013 17:06:09 -0000

Thanks Brian.
It was helpful indeed.
The GTI mapping is not mentioned in the RFC, it was confusing to only refer=
ence to ITU spec and wonder what should happen to ANSI.
I now understand that Encoding scheme is now derived from the "Number of di=
gits" parameter , if there are 5 octets and Number of digits is 9, then it =
is odd, if number of digits is 10, it is even and there cant be values othe=
r than 9/10 for a 5 octet digits parameter.

Regards,
Satya



-----Original Message-----
From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]=20
Sent: 15 January 2013 21:42
To: Nemana, Satya
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] Encoding scheme, Number of Digits parameters, GTI in=
 SUA message

Satya,

Please see comments inline...

Nemana, Satya wrote:                    (Mon, 14 Jan 2013 14:16:06)
> Hello!
>=20
> I had two questions trying to understand a problem with GT in SUA.
>=20
> 1) Why is the encoding scheme parameter normally present in the SS7=20
> messages absent in the SUA message as a parameter. In the absence of=20
> the encoding scheme in the SUA Called party GT, how does the SUA NIF=20
> analyze the digits.

They are always encoded as digits (i.e. nibble encoded digits) per RFC 3868=
/3.10.2.3.

> 2) The number of digits in the SUA message (called party) is already=20
> known depending on the digits included, i.e if I have a GT of=20
> 0123456789, then I have 10 digits. In such a situation where the=20
> number of digits present is implicitly known, why do we have an other=20
> parameter " Number of Digits" to tell the same? What is the=20
> significance of this parameter?

10 digits is not implicitly known unless it can be determined from the tran=
slation type.  5 octets of digits can be either 9 or 10 digits.  The odd/ev=
en indicator indicates this in SS7.  In SUA we used a full digit count (we =
had enough bits) instead of an odd/even indicator.  It avoids having to int=
erpret fillers and can be directly calculated off of the odd/even indicator=
 and the length of the digits (in octets).

> In most cases, GT is a phone number, why would we want to use only=20
> part of it for processing the message? (there would have been a=20
> wildcard GT provisioned for the destination(s) on the SG/STP to handle=20
> the case of using a subset of the digits.

The no. digits field does not encode a subset of the GT digits.  For exampl=
e, 5 octets of digits with a 'no. digits' field of 3 would be an
error: the field would have to be 9 or 10.

> 3) Also, in section 3.10.2.3, the text <snip>
> 0001 Nature of Address is taken over
> <snip>
> What does "taken over" mean? (Sorry, I don't mean the English meaning=20
> of it but taken over in this sentence : When there is an explicit=20
> Nature of Address parameter in SUA messages , I don't understand what=20
> is taken over here?)

It assumes the same value at the corresponding field in the SS7 SCCP
message: that is, it is "taken over" from the SS7 message.

> 4) ANSI specs and ITU specs for message format for different GTI=20
> values are different
>
> Example :
> ANSI GTI 1 : Global title includes translation type, numbering plan=20
> and encoding scheme ITU GTI 1 : global title includes nature of=20
> address indicator only SUA RFC only specifies ITU spec Q.713=20
> reference.
> Is it just for an example, and that similar formats should be used=20
> from ANSI or other specs wherever possible?
> Or is it to say that the format for the particular GTI is now=20
> redefined with the SUA spec and this should be used?

Read the line over the descripton of GTI values:

  "GTI (Global Title Indicator, defined in chapter 3.4.2.3 of Q.713)"

These _are_ the values of the ITU GTI.   ANSI defines fewer and more
restricted GTIs.  SUA uses the ITU GTIs and maps ANSI values into them.
ANSI GTI(1) maps into ITU GTI(3), ANSI GTI(2) maps into ITU GIT(2).

I hope that helps.

--brian

--
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/
