Re: Last Call: (IANA Reserved IPv4 Prefix for Shared Transition Space) to Informational RFC

2011-09-23 Thread Owen DeLong
On Sep 22, 2011, at 2:10 PM, George, Wes wrote: > -Original Message- > From: ietf-boun...@ietf.org [mailto:ietf-boun...@ietf.org] On Behalf Of Jari > Arkko > Sent: Thursday, September 22, 2011 2:35 PM > To: ietf@ietf.org; draft-weil-shared-transition-space-requ...@tools.ietf.org > Subjec

Re: Last Call: (IANA Reserved IPv4 Prefix for Shared Transition Space) to Informational RFC

2011-09-23 Thread Owen DeLong
On Sep 23, 2011, at 7:06 AM, George, Wes wrote: > -Original Message- > From: Owen DeLong [mailto:o...@delong.com] > Sent: Thursday, September 22, 2011 6:32 PM > To: George, Wes > Cc: Jari Arkko; ietf@ietf.org; > draft-weil-shared-transition-space-requ...@tools.ietf.o

Draft Weil and Draft BDGKS

2011-11-30 Thread Owen DeLong
will use some random mixture of all of the above in an uncoordinated and undefined way, making it impossible for vendors to provide any mitigation to such breakage. Respectfully Submitted, Owen DeLong Co-author draft-bdgks IPv6 Evangelist Director Professional Services Hurricane Electric Member, A

Re: Another last call for draft-weil

2012-02-14 Thread Owen DeLong
I support draft-weil as revised. There is a vital need for this to move forward and the IETF should stop standing in the way and let ARIN allocate the space already. Owen On Feb 13, 2012, at 10:09 AM, Chris Grundemann wrote: > Fellow BDGKS Authors, > > FYI: draft-weil is in another Last Call

Re: Last Call: (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP

2012-02-15 Thread Owen DeLong
>> +1 >> >> >>> I believe the amendments in this revision clarify the usage and intended >>> purpose of the shared transition space. >>> >> +1 >> >> > On 2/14/12 10:19 AM, jeff.finkelst...@cox.com wrote: >> &g

Re: [v6ops] Last Call: (Internet Protocol Version 6 (IPv6) Profile for 3GPP Mobile Devices) to Informational RFC

2013-08-21 Thread Owen DeLong
I also agree with James and Lorenzo. Owen On Aug 20, 2013, at 4:58 PM, james woodyatt wrote: > On Aug 20, 2013, at 02:39 , Lorenzo Colitti wrote: >> >> [...] It seems to me that the sheer length of the list, and the fact that is >> not prioritized, create a real risk that implementors will s

Re: [v6ops] Last Call: (Internet Protocol Version 6 (IPv6) Profile for 3GPP Mobile Devices) to Informational RFC

2013-09-10 Thread Owen DeLong
I have to agree with Lorenzo here again. This document seems to me to be: 1. Out of scope for the IETF. 2. So watered down in its language as to use many words to say nearly nothing. 3. Claims to be informational, but with so many caveats about the nature

Re: [v6ops] Last Call: (Internet Protocol Version 6 (IPv6) Profile for 3GPP Mobile Devices) to Informational RFC

2013-09-10 Thread Owen DeLong
On Sep 9, 2013, at 13:36 , Vízdal Aleš wrote: > Please see inline. > > Ales > > From: v6ops-boun...@ietf.org [mailto:v6ops-boun...@ietf.org] On Behalf Of > Owen DeLong > Sent: Monday, September 09, 2013 10:07 PM > To: mohamed.boucad...@orange.com > Cc: v6...

Re: [v6ops] Last Call: (Internet Protocol Version 6 (IPv6) Profile for 3GPP Mobile Devices) to Informational RFC

2013-09-12 Thread Owen DeLong
On Sep 11, 2013, at 02:40 , Abdussalam Baryun wrote: > On 9/9/13, Owen DeLong wrote: >> I have to agree with Lorenzo here again. >> >> This document seems to me to be: >> >> 1. Out of scope for the IETF. > > Please define what is the IETF