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 12:55:27 CEST 2016
Anno domini 2016 David Croft scripsit: > Strong support in principle. We have been denied IPv6 temporary > assignments due to the NCC's interpretation that a single DHCP lease > on wifi is a "subassignment" to another entity, which was clearly not > the intention. Thanks for the support. > 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? Best Max -- <@Placebox> Gibts eigentlich IRGENDWAS im IT-Bereich, was nicht a priori komplett scheiße ist? <@Zugschlus> all software sucks
- 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 ]