This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[address-policy-wg] 2016-04 New Policy Proposal (IPv6 PI Sub-assignment Clarification)
- Previous message (by thread): [address-policy-wg] 2016-04 New Policy Proposal (IPv6 PI Sub-assignment Clarification)
- Next message (by thread): [address-policy-wg] 2016-04 New Policy Proposal (IPv6 PI Sub-assignment Clarification)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Maximilian Wilhelm
max at rfc2324.org
Fri Oct 21 18:19:50 CEST 2016
Anno domini 2016 David Croft scripsit: > On 21 October 2016 at 12:55, Maximilian Wilhelm <max at rfc2324.org> wrote: > > Anno domini 2016 David Croft scripsit: > >> I note that the "New policy text" does not specify the replacement > >> text for the "Contractual Requirements" > > > > That doesn't seem neccessary as the point in question - the definiton > > of a sub-assignment - is specified in the new version of ripe-655. > > > > What are you missing? > > It appears in the "Current policy text" section, which implied that it > was going to be changed in the "New policy text" section, but I guess > it's just there for context then. Yes, indeed. I quoted that part as it is relavant context for the change and holds the point in questions. Best Max -- "Wer nicht mehr liebt und nicht mehr irrt, der lasse sich begraben." -- Johann Wolfgang von Goethe
- Previous message (by thread): [address-policy-wg] 2016-04 New Policy Proposal (IPv6 PI Sub-assignment Clarification)
- Next message (by thread): [address-policy-wg] 2016-04 New Policy Proposal (IPv6 PI Sub-assignment Clarification)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]