Subject: [Pana] NEW: [issue65] Clarification on simultaneous per-packet protection

From: [email-masked]
Date: Tue, 10 Feb 2004 09:09:46 +0200

TmV3IHN1Ym1pc3Npb24gZnJvbSBEYW4gRm9yc2JlcmcgPGRhbi5mb3JzYmVyZ0Bub2tpYS5jb20+Og0KDQo5LjQuNSBQcm90ZWN0aW9uLUNhcGFiaWxpdHkgQVZQDQoNCiAgIFRoZSBQcm90ZWN0aW9uLUNhcGFiaWxpdHkgQVZQIChDb2RlIDEwMjgpIGlzIG9mIHR5cGUgVW5zaWduZWQzMi4gIFRoZQ0KICAgQVZQIGRhdGEgaXMgdXNlZCBhcyBhIGNvbGxlY3Rpb24gb2YgZmxhZ3MgZm9yIGRpZmZlcmVudCBkYXRhDQogICBwcm90ZWN0aW9uIGNhcGFiaWxpdHkgaW5kaWNhdGlvbnMuIEJlbG93IGlzIGEgbGlzdCBvZiBzcGVjaWZpZWQgZGF0YQ0KICAgcHJvdGVjdGlvbiBjYXBhYmlsaXRpZXM6DQoNCiAgICAgICAgIDAgICAgICAgICAgVU5LTk9XTg0KICAgICAgICAgMSAgICAgICAgICBMMl9QUk9URUNUSU9ODQogICAgICAgICAyICAgICAgICAgIElQU0VDX1BST1RFQ1RJT04NCg0KDQpKQVJJOiAoVGVjaG5pY2FsKSBBcmUgdGhlc2UgaW50ZWdlcnMgb3IgYml0cz8gQ2FuIHlvdSBoYXZlIGEgY2FwYWJpbGl0eQ0KICAgICAgZm9yIGJvdGggTDIgYW5kIElQc2VjIHByb3RlY3Rpb24/DQoNCk5vdGUgYnkgQWxwZXI6IFRoZXNlIGFyZSBzdXBwb3NlZCB0byBiZSBpbnRlZ2Vycy4gVGhlIGN1cnJlbnQgZGVzaWduIGFzc3VtZXMNCm9ubHkgb25lIG9mIHRoZXNlIHdpbGwgYmUgZW5hYmxlZCAoVU5LTk9XTiBtZWFuaW5nIC4uLj8hPykgYWZ0ZXIgUEFOQS4gV2UNCnNoYWxsIGNsYXJpZnkgdGhpcyBpbiB0aGUgdGV4dC4NCg0KLS0tLS0tLS0tLQ0KY2F0ZWdvcnk6IFRlY2huaWNhbA0KZG9jdW1lbnQ6IGRyYWZ0LWlldGYtcGFuYS1wYW5hLXh4LnR4dA0KbWVzc2FnZXM6IDIwNw0Kbm9zeTogZGZvcnNiZXINCnByaW9yaXR5OiBTaG91bGQgRml4DQpzdGF0dXM6IENsYXJpZnlpbmcgVGV4dCBSZXF1aXJlZA0KdGl0bGU6IENsYXJpZmljYXRpb24gb24gc2ltdWx0YW5lb3VzIHBlci1wYWNrZXQgcHJvdGVjdGlvbg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NClBBTkEgSXNzdWVzIDxwYW5hX2lzc3Vlc0BkYW5mb3JzYmVyZy5pbmZvPg0KPGh0dHA6Ly9kYW5mb3JzYmVyZy5pbmZvOjgwODAvcGFuYS1pc3N1ZXMvaXNzdWU2NT4NCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo=_______________________________________________Pana mailing [email-masked]://www1.ietf.org/mailman/listinfo/pana

---

From: Yoshihiro Ohba <[email-masked]>
Date: Thu, 12 Feb 2004 12:48:14 -0800

On Tue, Feb 10, 2004 at 09:09:46AM +0200, [email-masked] wrote:
> New submission from Dan Forsberg <[email-masked]>:
> 
> 9.4.5 Protection-Capability AVP
> 
>    The Protection-Capability AVP (Code 1028) is of type Unsigned32.  The
>    AVP data is used as a collection of flags for different data
>    protection capability indications. Below is a list of specified data
>    protection capabilities:
> 
>          0          UNKNOWN
>          1          L2_PROTECTION
>          2          IPSEC_PROTECTION
> 
> 
> JARI: (Technical) Are these integers or bits? Can you have a capability
>       for both L2 and IPsec protection?
> 
> Note by Alper: These are supposed to be integers. The current design assumes
> only one of these will be enabled (UNKNOWN meaning ...?!?) after PANA. We
> shall clarify this in the text.

I agree.  The wording "a collection of flags" is incorrect.  Also, we
can delete the UNKNOWN code.  What about this?

"
The Protection-Capability AVP (Code 1028) is of type Unsigned32.  The
AVP data indicates the data protection capability supported by
EP.  Below is a list of specified data protection capabilities:

          1          L2_PROTECTION
          2          IPSEC_PROTECTION
"

Yoshihiro Ohba

> 
> ----------
> category: Technical
> document: draft-ietf-pana-pana-xx.txt
> messages: 207
> nosy: dforsber
> priority: Should Fix
> status: Clarifying Text Required
> title: Clarification on simultaneous per-packet protection
> __________________________________________________
> PANA Issues <[email-masked]>
> <http://danforsberg.info:8080/pana-issues/issue65>
> __________________________________________________

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

---

From: Yoshihiro Ohba <[email-masked]>
Date: Thu, 12 Feb 2004 12:48:14 -0800

"

          1          L2_PROTECTION
          2          IPSEC_PROTECTION
"

Yoshihiro Ohba

---

From: Jari Arkko <[email-masked]>
Date: Thu, 12 Feb 2004 23:10:48 +0200

> EP.  Below is a list of specified data protection capabilities:

Ok. Thanks.

--Jari

---

From: Jari Arkko <[email-masked]>
Date: Thu, 12 Feb 2004 23:10:48 +0200

Ok. Thanks.

--Jari