Re: [Sigtran] M3UA - Clarification on RFC 1.3.2.1
"Brian F. G. Bidulock" <bidulock@openss7.org> Mon, 08 August 2011 21:10 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 2A87B21F8BE5 for <sigtran@ietfa.amsl.com>; Mon, 8 Aug 2011 14:10:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.213
X-Spam-Level:
X-Spam-Status: No, score=-2.213 tagged_above=-999 required=5 tests=[AWL=-0.214, 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 d-3yxmLdmOuA for <sigtran@ietfa.amsl.com>; Mon, 8 Aug 2011 14:10:26 -0700 (PDT)
Received: from gw.openss7.com (gw.openss7.com [206.75.117.178]) by ietfa.amsl.com (Postfix) with ESMTP id 1F96621F8BDB for <sigtran@ietf.org>; Mon, 8 Aug 2011 14:10:25 -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 p78LAjGG008625; Mon, 8 Aug 2011 15:10:45 -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 p78LAjre016679; Mon, 8 Aug 2011 15:10:45 -0600
Received: (from brian@localhost) by wilbur.pigworks.openss7.net (8.14.3/8.14.3/Submit) id p78LAi6o016678; Mon, 8 Aug 2011 15:10:44 -0600
Date: Mon, 08 Aug 2011 15:10:44 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: aditi someshwar <aditi.someshwar@gmail.com>
Message-ID: <20110808211044.GA15848@openss7.org>
Mail-Followup-To: aditi someshwar <aditi.someshwar@gmail.com>, sigtran@ietf.org
References: <CAH62GXQBoK=RzM7wKJNi3jZeuC2ydyB8=K25JE-MS0sRTu2Jiw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CAH62GXQBoK=RzM7wKJNi3jZeuC2ydyB8=K25JE-MS0sRTu2Jiw@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)
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] M3UA - Clarification on RFC 1.3.2.1
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: Mon, 08 Aug 2011 21:10:27 -0000
aditi,
Well, no, the purpose is to extend the MTP/MTP-User interface from one
host to another. To do so, transporting the primitive is required, not
just the payload of the primitive.
--brian
aditi someshwar wrote: (Mon, 08 Aug 2011 13:47:42)
> RFC4666
>
> 1.3.2.1. Support for the Transport of MTP3-User Messages
>
> Fact (Quote): The M3UA layer provides the transport of MTP-TRANSFER
> primitives across an established SCTP association between an SGP and an
> ASP or between IPSPs.
>
> QUERY: The RFC seems to suggest that "MTP-TRANSFER PRIMITIVE itself" is
> transported between NODE-A & NODE-B; our belief is that the
> "CONSEQUENCE(result)" of having acted upon a primitive is what is
> transported - - meaning that the PAYLOAD passed over by the "MTP-3
> User" under the primitive "MTP-TRANSFER" is what gets transported.
>
> COMMENT: In a LOGICAL sense, OF COURSE, it would mean that when AT THE
> SENDING NODE, the "MTP-3 User" passes down a PAYLOAD to its LOCAL
> M3UA (requesting for its TRANSPORT to the remote nodeB), the M3UA
> does ACTION this, & with help from SCTP, causes this PAYLOAD to be
> transported across. At the receiving node, the M3UA shall get the
> PAYLOAD from its local SCTP, which it will in-turn handover to the
> UL {"MTP-3 User at node B"}. TO THAT EXTENT, use of the phrase
> "transports MTP- TRANSFER PRIMITIVE" is perhaps understandable, BUT
> the fact remains that it is confusing!!!
>
>
>
> Any Comments please???
>
> Regards,
>
> Aditi
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www.ietf.org/mailman/listinfo/sigtran
--
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/
- [Sigtran] M3UA - Clarification on RFC 1.3.2.1 aditi someshwar
- Re: [Sigtran] M3UA - Clarification on RFC 1.3.2.1 Brian F. G. Bidulock