0323030352d30312d31340a.nosense.org]
>> Sent: Saturday, June 19, 2010 3:28 AM
>> To: George, Wes E IV [NTK]
>> Cc: Brian E Carpenter; 6man
>> Subject: Re: [Fwd: I-D Action:draft-carpenter-6man-flow-update-03.txt]
>>
>> Sorry for the (very) late response, fina
l, all of the other uses for the field
> appear to be niche applications, with limited utility.
>
> Yours,
> Joel
>
> George, Wes E IV [NTK] wrote:
> > -Original Message-
> > From: Mark Smith [mailto:i...@69706e6720323030352d30312d31340a.nosense.org]
> > Sent: Saturda
...@69706e6720323030352d30312d31340a.nosense.org]
Sent: Saturday, June 19, 2010 3:28 AM
To: George, Wes E IV [NTK]
Cc: Brian E Carpenter; 6man
Subject: Re: [Fwd: I-D Action:draft-carpenter-6man-flow-update-03.txt]
Sorry for the (very) late response, finally remembered to reply
Does there have to be a
-Original Message-
From: Mark Smith [mailto:i...@69706e6720323030352d30312d31340a.nosense.org]
Sent: Saturday, June 19, 2010 3:28 AM
To: George, Wes E IV [NTK]
Cc: Brian E Carpenter; 6man
Subject: Re: [Fwd: I-D Action:draft-carpenter-6man-flow-update-03.txt]
Sorry for the (very) late
Sorry for the (very) late response, finally remembered to reply.
On Fri, 7 May 2010 16:03:25 -0500
"George, Wes E IV [NTK]" wrote:
>
> -Original Message-
> From: ipv6-boun...@ietf.org [mailto:ipv6-boun...@ietf.org] On Behalf Of Brian
> E Carpenter
> Sent: Thursday, May 06, 2010 9:11 P
..@ietf.org [mailto:ipv6-boun...@ietf.org] On Behalf Of
> George, Wes E IV [NTK]
> Sent: Friday, May 07, 2010 5:03 PM
> To: Brian E Carpenter; 6man
> Subject: RE: [Fwd: I-D Action:draft-carpenter-6man-flow-update-03.txt]
>
>
> -Original Message-
> From: ipv6-boun.
cross multiple n
etworks.
Thanks
Wes George
-Original Message-
From: ipv6-boun...@ietf.org [mailto:ipv6-boun...@ietf.org] On Behalf Of George,
Wes E IV [NTK]
Sent: Friday, May 07, 2010 5:03 PM
To: Brian E Carpenter; 6man
Subject: RE: [Fwd: I-D Action:draft-carpenter-6man-flow-update-03.txt
> -Original Message-
> From: ipv6-boun...@ietf.org [mailto:ipv6-boun...@ietf.org] On
> Behalf Of Joel M. Halpern
> Sent: Friday, May 07, 2010 9:29 PM
> To: Brian E Carpenter
> Cc: 6man
> Subject: Re: [Fwd: I-D Action:draft-carpenter-6man-flow-update-03.txt]
>
-Original Message-
From: ipv6-boun...@ietf.org [mailto:ipv6-boun...@ietf.org] On Behalf Of Brian E
Carpenter
Sent: Thursday, May 06, 2010 9:11 PM
To: 6man
Subject: [Fwd: I-D Action:draft-carpenter-6man-flow-update-03.txt]
Secondly, it offers the WG a binary choice as the main decision:
> -Original Message-
> From: ipv6-boun...@ietf.org [mailto:ipv6-boun...@ietf.org] On
> Behalf Of Brian E Carpenter
> "There appear to be two viable approaches:
>1. Definitively forbid locally defined use of the flow label.
>Strengthen RFC 3697 to say that hosts SHOULD set a
Joel,
On May 7, 2010, at 07:28 MDT, Joel M. Halpern wrote:
> The more I think about "encouraging" locally defined use of the flow label,
> the less I like it.
>
> The basic problem is that in the context we are discussing, is for use by
> routers.
> If you have locally defined flow label usage,
Thomas, Christian,
I'm responding to both of you in a single message, since you both expressed
concern with choice 2, (locally-defined use of flow-labels), particularly in
the face of IPSec.
Let's first look at the situation as it stands today. Today, if hosts or IPSec
GW's sent IPSec ESP pac
On May 7, 2010, at 15:28, Joel M. Halpern wrote:
> The more I think about "encouraging" locally defined use of the flow label,
> the less I like it.
>
> The basic problem is that in the context we are discussing, is for use by
> routers.
> If you have locally defined flow label usage, then
> 1)
.
-Original Message-
From: ipv6-boun...@ietf.org [mailto:ipv6-boun...@ietf.org] On Behalf Of Joel M.
Halpern
Sent: Friday, May 07, 2010 6:29 AM
To: Brian E Carpenter
Cc: 6man
Subject: Re: [Fwd: I-D Action:draft-carpenter-6man-flow-update-03.txt]
The more I think about "encouraging&quo
The more I think about "encouraging" locally defined use of the flow
label, the less I like it.
The basic problem is that in the context we are discussing, is for use
by routers.
If you have locally defined flow label usage, then
1) Any vendor selling to an operator has to somehow manage to su
I haven't decided yet whether I can support choice 2.
However, should choice 2 be used, what is the recommendation when
IPsec is in use? The recommendation assumes access to port numbers and
the like, which are hidden when IPsec is in use.
This is particularly important when a packet exits one F
16 matches
Mail list logo
