[Megaco] comments about draft-ietf-megaco-naspkg-04.txt
Fernando Vallejo Lazaro <Fernando.Vallejo_Lazaro@alcatel.es> Tue, 23 April 2002 14:09 UTC
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18434 for <megaco-archive@odin.ietf.org>; Tue, 23 Apr 2002 10:09:28 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA01152; Tue, 23 Apr 2002 09:45:36 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA29398 for <megaco@ns.ietf.org>; Tue, 23 Apr 2002 09:22:50 -0400 (EDT)
Received: from sess01.rdp.asi.alcatel.es (sess01.rdp.asi.alcatel.es [159.23.144.5]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA16672 for <megaco@ietf.org>; Tue, 23 Apr 2002 09:22:45 -0400 (EDT)
Received: from sers002.rpi.ses.alcatel.es (sers002 [159.23.193.30]) by sess01.rdp.asi.alcatel.es (8.11.2/8.11.2) with ESMTP id g3NDMBY06902 for <megaco@ietf.org>; Tue, 23 Apr 2002 15:22:11 +0200 (MEST)
Received: from alcatel.es (sevsf075 [159.23.195.75]) by sers002.rpi.ses.alcatel.es (8.8.8+Sun/8.8.8) with ESMTP id PAA26030 for <megaco@ietf.org>; Tue, 23 Apr 2002 15:21:57 +0200 (MET DST)
Message-ID: <3CC55E05.47421F04@alcatel.es>
Date: Tue, 23 Apr 2002 15:13:41 +0200
From: Fernando Vallejo Lazaro <Fernando.Vallejo_Lazaro@alcatel.es>
Organization: ALCATEL
X-Mailer: Mozilla 4.74 [en] (X11; U; SunOS 5.6 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: Megaco <megaco@ietf.org>
Subject: [Megaco] comments about draft-ietf-megaco-naspkg-04.txt
References: <200204101213.IAA16176@ietf.org>
Content-Type: multipart/alternative; boundary="------------0261F6B4631AA9BA10FFD3A1"
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org
Hi all, After this draft I am still missing something... As RFC2805 states in 11.2.5 the protocol must support: " g. Ability for the MGC to direct the NAS to connect to a specific tunnel, for example to an LNS, or to an AAA server." But I cannot find a way using this package to indicate (from the MGC to the MG) the AAA server to use. I think that something like the following should be added in the BASE NAS PACKAGE: 5.1.3. Authentication server address PropertyId: aaaaddr Description: AAA server address where the MG must establish the session. Type: unicast address, as in SDP Defined in: Termination state for NAS Termination Characteristics: read/write 5.1.4. Authentication server port PropertyId: aaaport Description: AAA server port where the MG must establish the session. Type: integer Defined in: Termination state for NAS Termination Characteristics: read/write Maybe I am missing something too... Comments are welcome Fernando Vallejo Alcatel Spain Internet-Drafts@ietf.org wrote: > A New Internet-Draft is available from the on-line Internet-Drafts directories. > This draft is a work item of the Media Gateway Control Working Group of the IETF. > > Title : Megaco/H.248 NAS Package > Author(s) : J. Mitchell, t. Taylor, A. Whitton, R. Subramaniam > Filename : draft-ietf-megaco-naspkg-04.txt > Pages : 18 > Date : 09-Apr-02 > > This document is intended to satisfy the requirements in section > 11.2.5 of the Megaco/H.248 requirements document. It defines five > packages: > - the base NAS package contains properties and events supported by > all NAS terminations; > - the NAS Incoming package contains properties and events > supported by NAS terminations involved in calls initiated by the > circuit network; > - the NAS Outgoing package contains properties supported by NAS > terminations involved in calls outgoing to the circuit network; > - the NAS Control package contains an event supported by a NAS > Control termination, which allows the MG to indicate a request to > initiate a data connection to a terminal served by the switched > circuit network; > - the NAS ROOT package contains properties supported by an MG which > is also capable of supporting at least the NAS and NAS Incoming > packages. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-megaco-naspkg-04.txt > > To remove yourself from the IETF Announcement list, send a message to > ietf-announce-request with the word unsubscribe in the body of the message. > > Internet-Drafts are also available by anonymous FTP. Login with the username > "anonymous" and a password of your e-mail address. After logging in, > type "cd internet-drafts" and then > "get draft-ietf-megaco-naspkg-04.txt". > > A list of Internet-Drafts directories can be found in > http://www.ietf.org/shadow.html > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt > > Internet-Drafts can also be obtained by e-mail. > > Send a message to: > mailserv@ietf.org. > In the body type: > "FILE /internet-drafts/draft-ietf-megaco-naspkg-04.txt". > > NOTE: The mail server at ietf.org can return the document in > MIME-encoded form by using the "mpack" utility. To use this > feature, insert the command "ENCODING mime" before the "FILE" > command. To decode the response(s), you will need "munpack" or > a MIME-compliant mail reader. Different MIME-compliant mail readers > exhibit different behavior, especially when dealing with > "multipart" MIME messages (i.e. documents which have been split > up into multiple messages), so check your local documentation on > how to manipulate these messages. > > > Below is the data which will enable a MIME compliant mail reader > implementation to automatically retrieve the ASCII version of the > Internet-Draft. > > ------------------------------------------------------------------------ > Content-Type: text/plain > Content-ID: <20020409132359.I-D@ietf.org> -- Fernando Vallejo Lazaro Phone: +34 91 330 8279 SW Wireline ASD-Madrid ALCATEL
- [Megaco] I-D ACTION:draft-ietf-megaco-naspkg-04.t… Internet-Drafts
- [Megaco] comments about draft-ietf-megaco-naspkg-… Fernando Vallejo Lazaro
- [Megaco] Comments draft-ietf-megaco-naspkg-04.txt Christian Groves