Re: draft-ietf-6man-uri-zoneid-02

2012-08-14 Thread t . petch
- Original Message - From: "Dave Thaler" To: "Brian E Carpenter" Cc: ; "Bob Hinden" Sent: Saturday, August 11, 2012 6:14 PM > > -Original Message- > > From: ipv6-boun...@ietf.org [mailto:ipv6-boun...@ietf.org] On Behalf Of > > Brian E Carpenter > > Sent: Saturday, August 11, 2012

Re: draft-ietf-6man-uri-zoneid-02

2012-08-13 Thread Juergen Schoenwaelder
On Thu, Aug 09, 2012 at 02:31:24PM -0700, Stuart Cheshire wrote: > At the meeting in Vancouver, Dave Thaler made a point that I found > convincing: > > Where is the character set for IPv6 zone IDs specified? If we accept > that future interface names might include non-roman characters, then > we h

Re: draft-ietf-6man-uri-zoneid-02

2012-08-12 Thread Brian E Carpenter
On 11/08/2012 18:14, Dave Thaler wrote: >> -Original Message- >> From: ipv6-boun...@ietf.org [mailto:ipv6-boun...@ietf.org] On Behalf Of >> Brian E Carpenter >> Sent: Saturday, August 11, 2012 3:40 AM >> To: Dave Thaler >> Cc: Bob Hinden; ipv6@ietf.org

RE: draft-ietf-6man-uri-zoneid-02

2012-08-11 Thread Dave Thaler
> -Original Message- > From: ipv6-boun...@ietf.org [mailto:ipv6-boun...@ietf.org] On Behalf Of > Brian E Carpenter > Sent: Saturday, August 11, 2012 3:40 AM > To: Dave Thaler > Cc: Bob Hinden; ipv6@ietf.org > Subject: Re: draft-ietf-6man-uri-zoneid-02 > > Dav

Re: draft-ietf-6man-uri-zoneid-02

2012-08-11 Thread Brian E Carpenter
Dave, On 11/08/2012 03:59, Dave Thaler wrote: > Brian Carpenter writes: >> On 09/08/2012 22:31, Stuart Cheshire wrote: >>> At the meeting in Vancouver, Dave Thaler made a point that I found >>> convincing: >>> >>> Where is the character set for IPv6 zone IDs specified? >> RFC 4007 doesn't do so, b

RE: draft-ietf-6man-uri-zoneid-02

2012-08-10 Thread Dave Thaler
Brian Carpenter writes: > On 09/08/2012 22:31, Stuart Cheshire wrote: > > At the meeting in Vancouver, Dave Thaler made a point that I found > > convincing: > > > > Where is the character set for IPv6 zone IDs specified? > > RFC 4007 doesn't do so, but can be read to imply ASCII. How? RFC 4007 sa

Re: draft-ietf-6man-uri-zoneid-02

2012-08-10 Thread Brian E Carpenter
> (this is just supporting that you say that the parse must be tolerant of > a bare %) First please solve the mystery of how such a parser can tell whether %251 is an escaped "%1" or an unescaped "%251". IETF IPv6 working grou

Re: draft-ietf-6man-uri-zoneid-02

2012-08-10 Thread Michael Richardson
> "Stuart" == Stuart Cheshire writes: Stuart> This argues in support of what Microsoft already did: Encode Stuart> '%' as "% 25". okay. May a browser process the %-escaped UTF-8 in the interface name for the purpose of display them? If it does that, and a user then copies and pa

Re: draft-ietf-6man-uri-zoneid-02

2012-08-10 Thread Brian E Carpenter
Stuart, On 09/08/2012 22:31, Stuart Cheshire wrote: > At the meeting in Vancouver, Dave Thaler made a point that I found > convincing: > > Where is the character set for IPv6 zone IDs specified? RFC 4007 doesn't do so, but can be read to imply ASCII. draft-ietf-6man-uri-zoneid-02 is explicit th

Re: draft-ietf-6man-uri-zoneid-02

2012-08-02 Thread Kerry Lynn
On Thu, Aug 2, 2012 at 12:29 PM, Juergen Schoenwaelder < j.schoenwael...@jacobs-university.de> wrote: > On Thu, Aug 02, 2012 at 11:10:40AM +0100, Brian E Carpenter wrote: > > > > I see no value in introducing a new separator. > > > > The value is providing a long-term path to cut and paste. Otherw

Re: draft-ietf-6man-uri-zoneid-02

2012-08-02 Thread Juergen Schoenwaelder
On Thu, Aug 02, 2012 at 11:10:40AM +0100, Brian E Carpenter wrote: > > I see no value in introducing a new separator. > > The value is providing a long-term path to cut and paste. Otherwise, > I assume we would indeed choose the %25 approach. OK, I change my statement to: I do not believe tha

Re: draft-ietf-6man-uri-zoneid-02

2012-08-02 Thread Brian E Carpenter
On 01/08/2012 18:16, Juergen Schoenwaelder wrote: > On Wed, Aug 01, 2012 at 09:42:44AM -0700, Tassos Chatzithomaoglou wrote: >> Wouldn't it be an option to have all applications & systems accept >> as input both formats, but only give as output the new one? >> i.e. browsers already rewrite URIs. >

Re: draft-ietf-6man-uri-zoneid-02

2012-08-01 Thread Juergen Schoenwaelder
On Wed, Aug 01, 2012 at 09:42:44AM -0700, Tassos Chatzithomaoglou wrote: > Wouldn't it be an option to have all applications & systems accept > as input both formats, but only give as output the new one? > i.e. browsers already rewrite URIs. There are other standards that currently state that % is

Re: draft-ietf-6man-uri-zoneid-02.txt

2012-07-18 Thread Mark Andrews
In message , Stuart Cheshire wr ites: > On 16 Jul, 2012, at 20:50, Mark Andrews wrote: > > > Stuart, > > your mail client botched the Content-type line generation. > > You may want to report it. > > > > Content-type: image/png; x-unix-mode=0644; name=Whatis' > > "?.png"="" > > Conte

Re: draft-ietf-6man-uri-zoneid-02.txt

2012-07-18 Thread Stuart Cheshire
On 16 Jul, 2012, at 20:50, Mark Andrews wrote: Stuart, your mail client botched the Content-type line generation. You may want to report it. Content-type: image/png; x-unix-mode=0644; name=Whatis' "?.png"="" Content-transfer-encoding: base64 Content-disposition: inli