Re: [Sigtran] What is the need of routing context in M3UA

"Brian F. G. Bidulock" <bidulock@openss7.org> Sun, 18 August 2013 12:18 UTC

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 3B2A311E828C for <sigtran@ietfa.amsl.com>; Sun, 18 Aug 2013 05:18:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.999
X-Spam-Level:
X-Spam-Status: No, score=-5.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_12=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WKyu05sE1aG3 for <sigtran@ietfa.amsl.com>; Sun, 18 Aug 2013 05:18:01 -0700 (PDT)
Received: from gw.openss7.com (gw.openss7.com [142.59.210.7]) by ietfa.amsl.com (Postfix) with ESMTP id 0520C11E8289 for <sigtran@ietf.org>; Sun, 18 Aug 2013 05:18:00 -0700 (PDT)
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 r7ICHvAL006503; Sun, 18 Aug 2013 06:17:57 -0600
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 r7ICHvMJ001532; Sun, 18 Aug 2013 06:17:57 -0600
Received: (from brian@localhost) by wilbur.pigworks.openss7.net (8.14.3/8.14.3/Submit) id r7ICHvIh001531; Sun, 18 Aug 2013 06:17:57 -0600
Date: Sun, 18 Aug 2013 06:17:57 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Norah Jones <nh.jones01@gmail.com>
Message-ID: <20130818121756.GA1435@openss7.org>
Mail-Followup-To: Norah Jones <nh.jones01@gmail.com>, sigtran@ietf.org
References: <abcd1234abc123ab12a0000009745000020000005002@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <abcd1234abc123ab12a0000009745000020000005002@gmail.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
Subject: Re: [Sigtran] What is the need of routing context in M3UA
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: Sun, 18 Aug 2013 12:18:17 -0000

Norah,

RC is a numerical index that identifies a routing key.  See
RFC 4666/1.4.2.1 Page 14.

BTW: you should be reading RFC 4666 instead of RFC 3332.

--brian

Norah Jones wrote:                         (Sun, 18 Aug 2013 06:19:46)
> Hi, 
> 
> Going thought the RFC 3332 and have a doubt about RC, in M3UA we have
> a concept of routing context to identify an AS but same can be achieve
> by the routing Key (it seems) then what the purpose RC is serving.
> 
> Thanks,
> Norah Jones

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