Thanks, Martin. Unless there are objections I'll reflect these in -01. Reminder to other implementors --
Finally, we invite implementors who have used values in the range 128-255 to contribute to this draft, so that the values can be included in the registry. Thanks, --John On Nov 7, 2018, at 12:38 AM, Martin Djernaes <[email protected]<mailto:[email protected]>> wrote: Hi I want to confess on the behalf of Juniper that we have "old" capabilities for refresh on 128 and ORF on 130 so they hopefully both will be reserved and we will not see trouble from implementations. Martin From: Idr <[email protected]<mailto:[email protected]>> On Behalf Of Susan Hares Sent: Wednesday, October 3, 2018 16:27 To: [email protected]<mailto:[email protected]> Cc: [email protected]<mailto:[email protected]> Subject: [Idr] draft-scudder-idr-capabilities-registry-change-02 - has been adopted Greetings: The WG has adopted draft-scudder-idr-capabilities-registry-change-02.txt. The authors should submit this as draft-ietf-idr-capabilities-registry-change-00.txt. Are the authors ready for WG last call on this document? In preparation for a WG LC, the authors should indicate if they know of any IPR regarding the draft. (My apologies for the repeated IPR call but I do not want to miss a process step with this draft. I would like this document go as swiftly as the IDR/Grow WG desires). Susan Hares _______________________________________________ GROW mailing list [email protected]<mailto:[email protected]> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_grow&d=DwICAg&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=hLt5iDJpw7ukqICc0hoT7A&m=DpD2Y53P0Is4IraxkJ4JirEGE3eyS8S2JadxLHnj8JU&s=CMG0TQrPDBT0bz0PTT5ND8_Qeuf2HPBOEUX4vIWdOE4&e=
_______________________________________________ GROW mailing list [email protected] https://www.ietf.org/mailman/listinfo/grow
