>> And you talked about Stuart Cheshire described a couple of IETFs ago,
>> Could you help to point out the link?
>
> Sadly, I don't have it, but I suspect Stuart does, and I'm pretty sure he's
> reading this.
Thanks, let's see whether he is going to talk here.
> The gist of what he was saying is
On Apr 19, 2009, at 7:46 AM, Hui Deng wrote:
And you talked about Stuart Cheshire described a couple of IETFs ago,
Could you help to point out the link?
Sadly, I don't have it, but I suspect Stuart does, and I'm pretty sure
he's reading this.
The gist of what he was saying is that if you ha
Hi, Ted,
Excuse me for my late comment, I try to catch this thread.
For the case of the device has two interfaces which originate query.
Your suggestion looks quite interesting: try every plausible way.
I guess this is interesting topic in MIF future work.
And you talked about Stuart Cheshire des
I would be in favor of stating explicitly that this issue is outside the
scope of the specification at hand.
Jari
___
Gen-art mailing list
Gen-art@ietf.org
https://www.ietf.org/mailman/listinfo/gen-art
On Apr 15, 2009, at 2:12 PM, Bernie Volz (volz) wrote:
My "vote" would be no change. But, I'd be OK if Ralph wanted to
state it
is TBD and outside the scope of this document and perhaps indicate
that
it is an issue whether the RG gets options to pass on from either the
container option or fro
My "vote" would be no change. But, I'd be OK if Ralph wanted to state it
is TBD and outside the scope of this document and perhaps indicate that
it is an issue whether the RG gets options to pass on from either the
container option or from those supplied to the RG.
- Bernie
-Original Message
Excerpts from Ted Lemon on Tue, Apr 14, 2009 02:48:06PM -0700:
> I don't mean to minimize this issue - if in fact there is some
> future real-world scenario where this would be a serious problem,
> it would be good if we could anticipate it.
I'm just saying the WG should make an explicit deci
On Apr 14, 2009, at 3:31 AM, Ralph Droms wrote:
Now, I admit I'm describing a hypothetical and abstract scenario. I
don't have a specific example of a situation in which a host might
make decisions - either in the stack or in an application or ??? -
about outbound traffic based on knowledge of
Ted - I think it's just as likely for the RG to get different
information from different interfaces (or different "administrative
domains") as it is for a host to get get different information
directly. Traffic from the host, which is then forwarded by the RG to
one of more than one possib
While this is certainly an interesting point, I don't really see that it
is specific to the container option or that the container option adds
any new or different issues?
I don't see why this would hold up this draft (perhaps it is not holding
it up)? Perhaps at most some statement(s) about the i
How realistic is it anyway that an RG would get different *relevant*
options on its different interfaces? This would seem to me to be an
administrative error. Of course the broadcast address and subnet
mask options might be different, but it doesn't make sense to send the
RG, e.g., diff
Hi Ralph -
Yup.. we've been at this way too long.
On the matter at hand:
Both of these documents allow a bit of twiddling with what gets sent to the
ultimate end client. The DHCP relay agent does this indirectly by signally
which branch of the network tree it exist in so the upstream DHCP ser
Hi, Ralph,
I agree what you said here, Scott raised the possible issue how to
differentiate the source.
One instant thinking about the two different 802.11 interface is that
the principal source policy selection will not be able to tell the
diffference, we could allow high level policy to recomme
Hui - I think there is an issue for hosts with multiple interfaces
triggered by Scott's comments about the container option: even if a
host is physically aware that it has multiple interfaces, how does it
take the characteristics of the networks behind those interfaces into
account when it
Mike - Can you give a little more detail? I'm not sure I see how the
RFC 3046 options - passed between a relay agent and a server - would
interact with the container option.
BTW, please feel free to join the conversation at any time. The SF
meeting marked the 20th year anniversary of the
Hi, Scott,
Based on the current MIF charter proposal, it consider only host.
http://www.ietf.org/mail-archive/web/mif/current/msg00367.html
I am wondering whether RG is a kind of host?
Anyhow, this discussion benefit MIF for the future consideration how
to identify the source.
Many thanks
-Hui
16 matches
Mail list logo