Subject: [Megaco] Packages a Physical Termination Supports

From: Carl Rutter <[email-masked]>
Date: Tue, 23 Apr 2002 10:38:21 -0400

If you have DS0s that support difference Packages
how is that conveyed to the MGC.
I would have thought AuditCapabilities but it doesn't support
packages?

Thx,
Carl

-----Original Message-----
From: Tom-PT Taylor [mailto:[email-masked]]
Sent: Tuesday, April 23, 2002 9:57 AM
To: 'Fernando Vallejo Lazaro'; Megaco
Subject: RE: [Megaco] comments about draft-ietf-megaco-naspkg-04.txt

Thank you for your comments.  I'll look into adding these fields, perhaps
after examination of Diameter to see how requests are routed.

-----Original Message-----
From: Fernando Vallejo Lazaro [mailto:[email-masked]]
Sent: Tuesday, April 23, 2002 9:14 AM
To: Megaco
Subject: [Megaco] comments about draft-ietf-megaco-naspkg-04.txt

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 
  
[email-masked] 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: 
        [email-masked]. 
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:     <[email-masked]>
-- 
Fernando Vallejo Lazaro
Phone:  +34 91 330 8279
SW  Wireline ASD-Madrid
       ALCATEL

_______________________________________________
Megaco mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/megaco

_______________________________________________
Megaco mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/megaco