IETF Logo Mail Archive

Re: [Sigtran] Conceptual doubt between an ASP and SGP

"Brian F. G. Bidulock" <bidulock@openss7.org> Thu, 13 March 2014 13:39 UTC

Return-Path: <bidulock@openss7.org>
X-Original-To: sigtran@ietfa.amsl.com
Delivered-To: sigtran@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E2E11A094C for <sigtran@ietfa.amsl.com>; Thu, 13 Mar 2014 06:39:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fcvvveFIxLLu for <sigtran@ietfa.amsl.com>; Thu, 13 Mar 2014 06:39:12 -0700 (PDT)
Received: from gw.openss7.com (gw.openss7.com [142.59.210.7]) by ietfa.amsl.com (Postfix) with ESMTP id D94431A0970 for <sigtran@ietf.org>; Thu, 13 Mar 2014 06:39:11 -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 s2DDd3KX022481; Thu, 13 Mar 2014 07:39:03 -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 s2DDd3QD021008; Thu, 13 Mar 2014 07:39:03 -0600
Received: (from brian@localhost) by wilbur.pigworks.openss7.net (8.14.3/8.14.3/Submit) id s2DDd21Y021007; Thu, 13 Mar 2014 07:39:02 -0600
Date: Thu, 13 Mar 2014 07:39:02 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Ajay Garg <ajaygargnsit@gmail.com>
Message-ID: <20140313133902.GA20110@openss7.org>
Mail-Followup-To: Ajay Garg <ajaygargnsit@gmail.com>, sigtran@ietf.org
References: <CAHP4M8VFfMjLXGQ703yL+Ne7Dujf7GmxOjJY+Ndvzn9k5K553Q@mail.gmail.com> <20140313071729.GB15132@openss7.org> <CAHP4M8VbbdprFv-AAfuu43fpwp3fskk4CZ6v2Xfaw_g2=MdfeQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAHP4M8VbbdprFv-AAfuu43fpwp3fskk4CZ6v2Xfaw_g2=MdfeQ@mail.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)
Archived-At: http://mailarchive.ietf.org/arch/msg/sigtran/YO8EsBMQlB09OzveMCG26Fq7r6c
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] Conceptual doubt between an ASP and SGP
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.1.15
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: Thu, 13 Mar 2014 13:39:15 -0000

Ajay,

Please see comments below...

Ajay Garg wrote:                               (Thu, 13 Mar 2014 15:34:38)
>    Brian,
>    RFC-2719 seems to be too technical for the use-case we are trying to
>    understand :)
>    I would rather present (a simplified version of) our use-case.
>    *
>    We have 3 nodes - N1, N2, N3.
>    *
>    We need to transfer messages in-between N1 and N3.
>    *
>    There is an IPSP-IPSP association each between between N1 <-> N2, and
>    N2 <-> N3 (but no IPSP-IPSP association between N1 <-> N3).
>    *
>    Also, provisions for GTT are available at each of N1, N2 and N3.
>    Theoritically/Practically, would the above configuration work? Or is it
>    necessary to have a SGP configured at N2?
>    Looking forward to clarifications.

M3UA IPSP only supports point to point and does not support a transfer
function in the middle.

SUA supports what you are attempting.

--brian

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

v2.8.7 | Report a Bug | By Email