In message <CAKD1Yr2xgkEeK7SaRjMZSbdJPs0u5FTozo0qa5MA4fda+SBcyw@xxxxxxxxxxxxxx>, Lorenzo Colitti writes: > On Sat, Feb 4, 2012 at 01:35, Fred Baker <fred@xxxxxxxxx> wrote: > > > The IESG again decided it needed a revised draft, and that draft - in > > large part, a rewrite - arrived in October. v6ops had a second WGLC, in > > which you again declined to comment, although you may have seen Lorenzo's > > comments, which were picked up in a November version of the draft. Ralph > > and Jari finally cleared their "discuss" ballots a couple of weeks ago, and > > we are having a second IETF last call. > > > > I'd like to understand your objective here. I know that you don't care for > > the draft, and at least at one point took it as a somewhat-personal attack. > > Is your objective to prevent the draft's publication entirely, or do you > > think that there is value in publishing it given a productive response to > > this comment? At what point are you willing to either participate in the > > public dialog or choose to not comment at all? > > > Ok, let me see if I can rephrase Erik's objection. > > The draft needs to take World IPv6 Launch into account, because it's a key > piece of the puzzle. > > We can't publish an RFC on how to transition content to IPv6 if the RFC > ignores the event when 5 of the top 10 websites in the world (and probably > many more) will permanently enable IPv6 for everyone. > > Cheers, > Lorenzo World IPv6 day just means Google is at 5.5 now and will go to 5.6/5.7. It really does not change anything. The decision to whitelist is a subjective one, not a objective one. Similarly the decision to stop whitelisting is also a subjective one. While I, and I suspect most of the list, think that whitelisting should no longer be needed that isn't our call to make. All we can do is encourage people to not whitelist by running dual stack services without using whitelisting. Mark -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: marka@xxxxxxx _______________________________________________ Ietf mailing list Ietf@xxxxxxxx https://www.ietf.org/mailman/listinfo/ietf