Re: [ippm] draft-morton-ippm-owamp-registry call for adoption and draft-elkins-ippm-6man-pdm-option accepted for adoption

["MORTON, ALFRED C (AL)" <[e-mail]>]

Hi Mike,
thanks for your review, please see my replies below.

From: Ackermann, Michael [mailto:[e-mail]]
Sent: Friday, June 19, 2015 10:53 AM
To: Bill Cerveny; [e-mail]
Cc: MORTON, ALFRED C (AL)
Subject: RE: [ippm] draft-morton-ippm-owamp-registry call for adoption and draft-elkins-ippm-6man-pdm-option accepted for adoption

HI Bill

I did read the draft.   My initial comments (hopefully in the format you wanted),  are below.


a.)    I do support the addition of the milestone and believe  the adoption
of this draft as a WG item will fulfill that milestone .

b.)    Yes,  I have read the draft.

c.)     I pledge to review the draft during the WG Process.

I also have the following related questions/comments:

1.       In 3.1.4, is the Command Control Numbers listing exhaustive?    Can it be added to or changed as needed later?

[ACM]

Yes. If we want to add new commands, we can do this by defining the

command(s) in an RFC, and then requesting IANA to assign a new number in

the registry corresponding to the new command.  This is the same

approximate procedure you will follow with the PDM draft, I suppose

the IPv6 destination options have a corresponding registry, and IPPM

would need to request to register the PDM option.



2.       Same question as above, only for 3.2.4.   Are the Modes exhaustive or granular enough?

[ACM]

Again it’s yes, new Modes can also be added.

Do we need to differentiate:   specific types of Authentication or Encryption, or modes of IPsec operation?  (random examples).   And once again can this be added to as needed at a later time?

[ACM]

Either the new feature or extension needs to be completely specified in the

the RFC that describes it – or – it must specify some other means to achieve

compatible operation, probably the controls specified in an existing RFC.

3.       Again in 3.2.4, the statement about the OWAMP and TWAMP registry value assignments functioning differently.   In general, for simplicity and ease of use purposes, I would be in favor of keeping  as many registry functions and values as similar as possible, across all disciplines utilizing registry functions.   This particular area of registry value assignment sounds to me to be more effectively performed in OWAMP and hence I would encourage TWAMP to change.     I am hoping this would have precedent setting influence.

[ACM]

I identified one case where we may want to be aligned, but mostly we can expect

differences between OWAMP and TWAMP. The RFC 5618 Mixed Security

Mode feature for TWAMP would also be easily applicable to OWAMP, but we need an

RFC to describe the feature and then request the reserved bit position

(which I already asked for reserved status).  I’ve added

and expanded version of the text that Nalini and you have suggested.

[ACM] thanks for your review and support!
Al

From: ippm [mailto:[e-mail]] On Behalf Of Bill Cerveny
Sent: Wednesday, June 10, 2015 4:55 PM
To: [e-mail]<mailto:[e-mail]>
Subject: [ippm] draft-morton-ippm-owamp-registry call for adoption and draft-elkins-ippm-6man-pdm-option accepted for adoption

Dear IPPM participants,

As noted in discussions for which the IPPM working group has been cc’ed on, draft draft-morton-ippm-owamp-registry-00, "Registries for the One-Way Active Measurement Protocol - OWAMP" has been proposed to establish an OWAMP registry.  The first mission of an OWAMP registry would be to support a registry entry for draft-ietf-ippm-ipsec, which is currently in IESG evaluation.

Please indicate:
(a) whether you support the addition of the milestone and the adoption
of the draft as a WG item to fulfill that milestone
(b) whether you have read the draft
(c) whether you pledge to review the draft during the WG process.

This working group last call runs for 2 weeks, but if there is sufficient support the draft may be accepted earlier so that draft-ietf-ippm-ipsec can progress.

Also, draft-elkins-ippm-6man-pdm-option has been accepted for adoption by the IPPM working group.

Regards,

Bill Cerveny
IPPM WG co-chair


The information contained in this communication is highly confidential and is intended solely for the use of the individual(s) to whom this communication is directed. If you are not the intended recipient, you are hereby notified that any viewing, copying, disclosure or distribution of this information is prohibited. Please notify the sender, by electronic mail or telephone, of any unintended receipt and delete the original message without making any copies.

Blue Cross Blue Shield of Michigan and Blue Care Network of Michigan are nonprofit corporations and independent licensees of the Blue Cross and Blue Shield Association.