Subject: [Megaco] Re: Question to H.248 gm Package (used by ES 283 018)

From: [email-masked]
Date: Sat, 15 Jul 2006 07:01:25 +0200

Hello Annie,

I may not answer your questions on selected data type (and wildcarding
possibilities) because I'm not familiar with the history of gm.
But I'd like to note that the gm package will be again discussed at next
WP2/16 meeting (in scope of H.248.gm work item). So, there is a chance in
review and revising again the package design.

- Albrecht

PS
The other TS 102 333 packages, diffserv, tman, mpls and vlan will be also
moved to ITU-T, see 11TD045.

######
Dear WP2/16 experts,

Please note that the meeting notice of Ottawa meeting and its
logistic information can be found at:

http://ftp3.itu.int/av-arch/avc-site/2005-2008/0608_Ott/Notice_Ottawa_0608.txt

http://ftp3.itu.int/av-arch/avc-site/2005-2008/0608_Ott/Ott_Invitation.doc

...

                      Annie Benitez                                                                                               
                      Pelaez                   To:      [email-masked]                                                  
                      <ABenitez@ACMEPA         cc:                                                                                
                      CKET.COM>                Subject: Re: Question to H.248 gm Package (used by ES 283 018)                     
                                                                                                                                  
                      14.07.2006 17:42                                                                                            
                      Please respond                                                                                              
                      to Annie Benitez                                                                                            
                      Pelaez                                                                                                      

Hello H.248 friends,

Hope all is well. Question regarding the gm package?

In order to perform source address filtering there are 2 properties (copied
below for convenience).

In order to perform filtering on a remote IP address typically there 2
things you need to provide:
a)       the remote IP address
b)       a IP address mask to determine how many bits need to be monitored
for filtering purposes.

There are 2 ways of doing this:
1)       RemoteAddress = 10.140.120.10 and a RemoteMask = 255.255.254.0, or
2)       RemoteAddressMask = 10.140.120.10/20 (i.e. only the 1st 20 bits
are applicable for that mask)

The issue is that the current Gate Management package only has a mask,
while it states that "*" may be used ? this seems restrictive as you can
only wildcard digits (the above example would not be possible). And if you
interpret it as a mask (something like 255.255.254.0) then what would be
the leading digits of the remote address? Would it come from the remote
descriptor? (if so again this is restrictive and assumes symmetrical
behaviour which is not always the case).

Any insight as to how this package was envisioned to work would help.
I would propose enhancing the package to include an attribute "number of
bits" as an integer that would indicate the number of bits of the "sam"
that are applicable for masking.

Many thanks,
Annie

Annie Benitez Pelaez
Product Management - Acme Packet
T: +1 (781) 328 4392
M: +1 (857) 222 3738
[email-masked]

Property Name: Remote Source Address Filtering.
PropertyID: saf (0x0001).
Description: This property indicates whether source address filtering shall
be enforced.
Type: Boolean.
Possible values: ON (Enforce source filtering);
OFF (no source filtering). Default value is OFF.
Defined in: Local Control.
Characteristics: Read/Write.

Property Name: Remote Source Address Mask.
PropertyID: sam (0x0002).
Description: This property indicates which source addresses are accepted
for packets received by the
termination.
Type: String.
Possible values: Encoded as a DomainAddress, as defined in ITU-T
Recommendation H.248.1 [1], annex B. "*" is
used as a wildcard for digits.
Defined in: Local Control.
Characteristics: Read/Write.

-----Original Message-----
From: Albrecht Schwarz [mailto:[email-masked]]
Sent: Saturday, March 04, 2006 10:10 AM
To: [email-masked]
Subject: Re: Question to H.248 gm Package (used by ES 283 018)

Thanks Christian for that pointer!

The Annex B ABNF syntax is so allowing to extend a single value towards
'lists' or a 'range'. Is there sth similar for H.248 using binary encoding?

Albrecht

                      Christian Groves
                      <Christian.Groves@NT         To:
[email-masked]
                      ECZONE.COM>                  cc:
                                                   Subject: Re: Question to
H.248 gm Package (used by ES 283 018)
                      02.03.2006 08:43
                      Please respond to
                      Christian Groves

Hello All,

H.248 allows you to specify ranges for parameter values natively. No
packages tricks required.
e.g.
H.248.1 Annex B ABNF Syntax
    parmValue            = (EQUAL alternativeValue / INEQUAL VALUE)

    alternativeValue        = (VALUE
                    / LSBRKT VALUE *(COMMA VALUE) RSBRKT
                        ; sublist (i.e. A AND B AND ...)
                    / LBRKT VALUE *(COMMA VALUE) RBRKT
                        ; alternatives (i.e. A OR B OR ...)
                    / LSBRKT VALUE COLON VALUE RSBRKT)
                        ; range

Regards, Christian

neal wrote:

>Hi Albrecht,
>   using higher 16 bits and low 16 bits of this 32 bits integer separately
>or define 2 properties for ranges?
>
>Neal
>----- Original Message -----
>From: "Albrecht Schwarz" <[email-masked]>
>To: <[email-masked]>
>Sent: Wednesday, March 01, 2006 6:53 PM
>Subject: Question to H.248 gm Package (used by ES 283 018)
>
>
>
>
>>Question:
>>How shall be the "Remote Source Port Range" property of the Gate
>>
>>
>Management
>
>
>>Package encoded?
>>The type of property gm/spr is "Integer", but the property is supporting
>>"value ranges".
>>
>>Present definition permits only filtering on individual ports, but not
>>ranges IMHO.
>>
>>Albrecht
>>
>>-------------------------------------------------------------------
>>Mail archive for TISPAN_WG3  can be browsed at the following url :
>>         http://list.etsi.org/TISPAN_WG3.html
>>-------------------------------------------------------------------
>>
>>
>
>-------------------------------------------------------------------
>Mail archive for TISPAN_WG3  can be browsed at the following url :
>         http://list.etsi.org/TISPAN_WG3.html
>-------------------------------------------------------------------
>
>
>
>
>
>

-------------------------------------------------------------------
Mail archive for TISPAN_WG3  can be browsed at the following url :
         http://list.etsi.org/TISPAN_WG3.html
-------------------------------------------------------------------

-------------------------------------------------------------------
Mail archive for TISPAN_WG3  can be browsed at the following url :
         http://list.etsi.org/TISPAN_WG3.html
-------------------------------------------------------------------

     Mail archive for TISPAN_WG3 can be browsed at the following url :

                   http://list.etsi.org/TISPAN_WG3.html

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