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

Norah Jones <nh.jones01@gmail.com> Sun, 18 August 2013 06:19 UTC

Return-Path: <nh.jones01@gmail.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 DC87011E8255 for <sigtran@ietfa.amsl.com>; Sat, 17 Aug 2013 23:19:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_12=0.6]
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 wASrjf6EFHZc for <sigtran@ietfa.amsl.com>; Sat, 17 Aug 2013 23:19:48 -0700 (PDT)
Received: from mail-pd0-x22d.google.com (mail-pd0-x22d.google.com [IPv6:2607:f8b0:400e:c02::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 8DE5F11E8254 for <sigtran@ietf.org>; Sat, 17 Aug 2013 23:19:48 -0700 (PDT)
Received: by mail-pd0-f173.google.com with SMTP id p10so3733923pdj.4 for <sigtran@ietf.org>; Sat, 17 Aug 2013 23:19:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:to:from:reply-to:subject:message-id:mime-version :content-transfer-encoding:content-type; bh=gPELRQqUjXmpVmrXEQNmHpIab926QtS9UZUiFTwWxRY=; b=Ay+hHzsqQ8c2flNtZgvDXfV3JLqqctooyyaNUVjB2ZudUMUCEL88lKKAYAKtoQr636 OkySJatHgK0I7rWs9xUppjYUJPYSDzuzDq3CZenNwjSmx79HcYiTDVxsTLD0iCVu6bDY pbHXE6kJMtUdmm5wMayhNes2wPOXxvPinGrQEBxCAvtCHhisf9HIoU0SG28uu78dLBtx Cn58zckvXa76IQ0GnkBHU40/oqa/cdUz1YKP8M790P01zNFCSnno/BlOv3uOKUgPJ8wV 3RjCO6KfuK1JacaT3JHKJbS64k0ryzOeFKlrJ9MTFLAXryg28VrUAbaa+o9oL29spkmh yu8g==
X-Received: by 10.66.122.41 with SMTP id lp9mr6573392pab.6.1376806788331; Sat, 17 Aug 2013 23:19:48 -0700 (PDT)
Received: from queryhome.com (ec2-54-245-79-134.us-west-2.compute.amazonaws.com. [54.245.79.134]) by mx.google.com with ESMTPSA id yk10sm7818890pac.16.1969.12.31.16.00.00 (version=TLSv1 cipher=RC4-SHA bits=128/128); Sat, 17 Aug 2013 23:19:47 -0700 (PDT)
Date: Sun, 18 Aug 2013 06:19:46 +0000
To: sigtran@ietf.org
From: Norah Jones <nh.jones01@gmail.com>
Message-ID: <abcd1234abc123ab12a0000009745000020000005002@gmail.com>
X-Priority: 3
X-Mailer: CatPHPMailer 5.1 (phpmailer.sourceforge.net)
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset="utf-8"
Subject: [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: Norah Jones <nh.jones01@gmail.com>
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 06:19:49 -0000

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