List Info

Thread: RE: Client IAADDR copying between Advertise and Request




RE: Client IAADDR copying between Advertise and Request
country flaguser name
United States
2007-03-30 19:48:50
>I've observed that all clients supply the IAADDR from
the advertise
>in their request - and I think that a client that
chooses not to is
>going to find themselves incompatible with servers that
are written
>'to the wire'.

Your quote on your signature is interestingly appropriate
for this
discussion and applies to those that don't read the RFC
carefully:

>David W. Hankins	"If you don't do it right the
first time,
>Software Engineer		you'll just have to do it
again." 

>> David, I beleive you commented something about the
transaction-id
being
>> the same for the Solicit and Request, but I don't
believe that is the
>> case at all:
>
>Nope.  Not sure what this is about.

Must have been someone else; sorry.

Cheers.

- Bernie

-----Original Message-----
From: David W. Hankins [mailtoavid_Han
kinsisc.org] 
Sent: Friday, March 30, 2007 7:37 PM
To: DHC WG
Subject: Re: [dhcwg] Client IAADDR copying between Advertise
and Request

On Fri, Mar 30, 2007 at 01:15:52PM -0400, Bernie Volz (volz)
wrote:
> Also, doesn't this create a special case for the
S/A/R/R sequence in
the
> server? That means that the server has to have some way
to detect that
> the Request is in response to an Advertise?

I think it doesn't change server behaviour.

You either use the supplied address as a hint, or you don't,
and
that's a separate debate.  You either support a client that
supplied
no addr (as rfc3315 says today), or you don't, and that's
also a
separate debate.

I've observed that all clients supply the IAADDR from the
advertise
in their request - and I think that a client that chooses
not to is
going to find themselves incompatible with servers that are
written
'to the wire'.

What the server does or doesn't do is immaterial.

> David, I beleive you commented something about the
transaction-id
being
> the same for the Solicit and Request, but I don't
believe that is the
> case at all:

Nope.  Not sure what this is about.

-- 
David W. Hankins	"If you don't do it right the first
time,
Software Engineer		you'll just have to do it again."
Internet Systems Consortium, Inc.	-- Jack T. Hankins

_______________________________________________
dhcwg mailing list
dhcwgietf.org
https://
www1.ietf.org/mailman/listinfo/dhcwg

Re: Client IAADDR copying between Advertise and Request
country flaguser name
United States
2007-03-30 20:54:57
On Fri, Mar 30, 2007 at 08:48:50PM -0400, Bernie Volz (volz)
wrote:
> Your quote on your signature is interestingly
appropriate for this
> discussion and applies to those that don't read the RFC
carefully:
> 
> >David W. Hankins	"If you don't do it right the
first time,
> >Software Engineer		you'll just have to do it
again." 

I think it also applies to RFC writers, especially those
who
are producing 'bis' documents.

-- 
David W. Hankins	"If you don't do it right the first
time,
Software Engineer		you'll just have to do it again."
Internet Systems Consortium, Inc.	-- Jack T. Hankins

_______________________________________________
dhcwg mailing list
dhcwgietf.org
https://
www1.ietf.org/mailman/listinfo/dhcwg

[1-2]

about | contact  Other archives ( Real Estate discussion Medical topics )