Re: M2PA Registered Ports

"Brian F. G. Bidulock" <bidulock@openss7.org> Sat, 02 October 2010 21:59 UTC

Return-Path: <bidulock@openss7.org>
X-Original-To: tsvwg@core3.amsl.com
Delivered-To: tsvwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 890943A6D5D for <tsvwg@core3.amsl.com>; Sat, 2 Oct 2010 14:59:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.5
X-Spam-Level:
X-Spam-Status: No, score=-2.5 tagged_above=-999 required=5 tests=[AWL=0.099, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Aoe7eG9ItBgT for <tsvwg@core3.amsl.com>; Sat, 2 Oct 2010 14:59:54 -0700 (PDT)
Received: from gw.openss7.com (gw.openss7.com [206.75.119.236]) by core3.amsl.com (Postfix) with ESMTP id 551BC3A6D35 for <tsvwg@ietf.org>; Sat, 2 Oct 2010 14:59:54 -0700 (PDT)
Received: from wilbur.pigworks.openss7.net (IDENT:/ORMDrsfNWZY/N9LTwKokvFx7NAWaX9o@ns5.evil.openss7.net [192.168.9.5]) by gw.openss7.com (8.13.8/8.13.8/Debian-3+etch1) with ESMTP id o92M0ffh022713; Sat, 2 Oct 2010 16:00:41 -0600
Received: from wilbur.pigworks.openss7.net (IDENT:k+6FArZaHbq3nAP7bmXyw5EdLHAa6AYd@localhost [127.0.0.1]) by wilbur.pigworks.openss7.net (8.13.8/8.13.8/Debian-3) with ESMTP id o92M0f3C032705; Sat, 2 Oct 2010 16:00:41 -0600
Received: (from brian@localhost) by wilbur.pigworks.openss7.net (8.13.8/8.13.8/Submit) id o92M0fUh032704; Sat, 2 Oct 2010 16:00:41 -0600
Date: Sat, 02 Oct 2010 16:00:41 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Nitin Kumar <nitin941981@gmail.com>
Subject: Re: M2PA Registered Ports
Message-ID: <20101002220041.GA32428@openss7.org>
Mail-Followup-To: Nitin Kumar <nitin941981@gmail.com>, tsvwg@ietf.org
References: <AANLkTik+KqNgeRaP5=XQ66MHgfGimV08e_o-rsgqHwwG@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <AANLkTik+KqNgeRaP5=XQ66MHgfGimV08e_o-rsgqHwwG@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.13 (2006-08-11)
Cc: tsvwg@ietf.org
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: bidulock@openss7.org
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 02 Oct 2010 21:59:55 -0000

Nitin,

See the IANA port number registration for M2PA: www.iana.org

--brian

Nitin Kumar wrote:                            (Fri, 01 Oct 2010 10:01:32)
> 
>    Hello Brian,
>    Thanks for your response.
>    But as mentioned in section 4.1.2 of RFC 4165:
>    "It is necessary for at least one of the endpoints to be listening on
>    the port on which the other endpoint is trying to establish the
>    association.  Therefore, at least one of the port numbers SHOULD be
>    the M2PA registered port."
>    Now when it refers to M2PA registered port, then what port it is
>    actually talking about. I mean which port i call as an M2PA registered
>    port?
>    Regards
>    Nitin

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