On Jun 1, 2011, at 4:42 PM 6/1/11, Thomas Narten wrote:
> Brian E Carpenter writes:
>
>> Ray,
>
>> Without going into details: how about turning this into
>> draft-hunter-v6ops-something and having the debate over in v6ops?
>
>> I think that would be useful, personally.
>
> Actually, let me
Brian E Carpenter writes:
> Ray,
> Without going into details: how about turning this into
> draft-hunter-v6ops-something and having the debate over in v6ops?
> I think that would be useful, personally.
Actually, let me suggest something else.
Before spending a whole lot of time on this topic
On May 31, 2011, at 6:41 PM, Mark Smith
wrote:
> On Tue, 31 May 2011 09:24:19 -0700
> james woodyatt wrote:
>
>> On May 30, 2011, at 7:38 PM, Fred Baker wrote:
>>>
>>> [...] IPv6 systems come, at least today, with SLAAC as the default. So
>>> there is a requirement to configure DHCPv6, a
On Tue, 31 May 2011 09:24:19 -0700
james woodyatt wrote:
> On May 30, 2011, at 7:38 PM, Fred Baker wrote:
> >
> > [...] IPv6 systems come, at least today, with SLAAC as the default. So
> > there is a requirement to configure DHCPv6, at least from that perspective.
> > That said, SLAAC ain't go
On May 30, 2011, at 10:38 PM 5/30/11, Fred Baker wrote:
>
> On May 30, 2011, at 3:57 PM, Ray Hunter wrote:
>
>> This is danger of going off topic I know (maybe it should go in v6ops), but
>> it's important to me to be able to understand the consequences of the
>> discussion, so please bear wi
Ray,
Without going into details: how about turning this into
draft-hunter-v6ops-something and having the debate over in v6ops?
I think that would be useful, personally.
Regards
Brian
On 2011-06-01 08:52, Ray Hunter wrote:
> Sorry a couple of important typos on RFC numbers: email escaped too
Sorry a couple of important typos on RFC numbers: email escaped too early.
Disregard previous message, and use this one.
Ray Hunter wrote:
It's definitely going to become an operational FAQ, unless it is very
clear whether/how a network operator can force equivalent use of
DHCPv4 static address
Ray Hunter wrote:
It's definitely going to become an operational FAQ, unless it is very
clear whether/how a network operator can force equivalent use of
DHCPv4 static address assignment for both source and destination
addresses via DHCPv6 (possibly by turning off SLAAC for assignment of
GUA on
On May 30, 2011, at 7:38 PM, Fred Baker wrote:
>
> [...] IPv6 systems come, at least today, with SLAAC as the default. So there
> is a requirement to configure DHCPv6, at least from that perspective. That
> said, SLAAC ain't gonna happen in the absence of RAs, and you can disable RAs
> on the r
On 31 May 2011, at 03:38, Fred Baker wrote:
>
> I would expect, however, that the use of DHCP is something configured on the
> system in question, just like it is in IPv4. Not that there is an
> auto-configure option in IPv4 - the other alternative is manual
> configuration, and most systems c
On May 30, 2011, at 3:57 PM, Ray Hunter wrote:
> This is danger of going off topic I know (maybe it should go in v6ops), but
> it's important to me to be able to understand the consequences of the
> discussion, so please bear with me. It's definitely going to become an
> operational FAQ, unles
This is danger of going off topic I know (maybe it should go in v6ops),
but it's important to me to be able to understand the consequences of
the discussion, so please bear with me. It's definitely going to become
an operational FAQ, unless it is very clear whether/how a network
operator can fo
On May 30, 2011, at 2:12 PM, Brian E Carpenter wrote:
> For example, setting the DSCP *as a function of
> the source address* makes me cringe. We're going to have to get used to
> the fact that IP addresses are not constants.
good grief. The only reasonable use of a DSCP is to identify the set o
Ray,
On 2011-05-31 08:05, Ray Hunter wrote:
...
> Which source address (SLAAC/DHCPv6) would be used by the client for an
> outbound session if a SLAAC address and a DHCPv6 were both configured on
> the same link and with the same prefix, in the absence of a flag?
Whichever RFC3484bis or the loca
14 matches
Mail list logo
