Subject: RE: [AAA-WG]: Issue 311:Acct-Application-Id and Vendor-Specific-Application-Id in ACR

From: <[email-masked]>
Date: Mon, 1 Apr 2002 22:58:50 +0300

Hi Jari,

Got the changes, some confirmations in-line.

John

> 5) Modify ANF for ACR as follows:
> 
>     <ACR> ::= < Diameter Header: 271, REQ, PXY >
>               < Session-Id >
>               { ... }
> 	     [ Acct-Application-Id ]
>               [ Vendor-Specific-Application-Id ]
> 	     [ ... ]

So, ACR  becomes:

<ACR> ::= < Diameter Header: 271, REQ, PXY >
          < Session-Id >
          { Origin-Host }
          { Origin-Realm }
          { Destination-Realm }
          { Accounting-Record-Type }
          { Accounting-Record-Number }
          [ Acct-Application-Id ]
          [ Vendor-Specific-Application-Id ]
          [ User-Name ]
          [ Accounting-Sub-Session-Id ]
          [ Accounting-RADIUS-Session-Id ]
          [ Acct-Multi-Session-Id ]
          [ Accounting-Interim-Interval ]
          [ Accounting-Realtime-Required ]
          [ Origin-State-Id ]
        * [ AVP ]
        * [ Proxy-Info ]
        * [ Route-Record ]

> 9) Modify AVP occurrence tables appropriately.

Is this correct:

Acct-Application-Id           | 0-1 | 0-1 |

Vendor-Specific-Application-Id| 0-1 | 0-1 |

> 
> 10) 6.1.1 add Vendor-Specific-Application-Id to the list in 
> the last bullet.
> 
> 11) Add a new paragraph after the first paragraph of 11.3: 
> "Both Application-Id
>     and Acct-Application-Id AVPs use the same Application 
> Identifier space."
> 
> 12) Also add to 11 that not just zero but also 0xffffffff are 
> reserved values.
> 
> 
>