Re: [mif] WG Review: Multiple InterFaces (mif)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Without addressing both issues, the user or application (or transport layer) can't utilize simultaneous networks. Thererfore, as far as I know, MIF tries to adress real-world problems for the network circumastances, it shoud adress both problems, preferably, as separate topics in the same group. Otherwise, a working group may need to address best common practice for simultaneous network utilization, but I think MIF should be the group though.

Giyeong 
--------------------------
Sent from my BlackBerry Wireless Handheld
 

----- Original Message -----
From: mif-bounces@xxxxxxxx <mif-bounces@xxxxxxxx>
To: IETF Discussion <ietf@xxxxxxxx>; MIF Mailing List <mif@xxxxxxxx>
Sent: Wed Apr 22 19:07:16 2009
Subject: Re: [mif] WG Review: Multiple InterFaces (mif)

Excerpts from Christian Vogt on Wed, Apr 22, 2009 04:03:39PM -0700:
> My main point, though, was that we are talking about two orthogonal
> issues -- conflicting configuration and address selection.  This
> holds independently of the fact that an application may let the
> operating system accomplish part or all of address selection.
>
> Whether we take this to mean that both issues should be tackled in
> the same working group is a different story.  I personally don't see
> the orthogonality of the two issues as a reason not to tackle both
> issues in the same working group.  We just ought to be aware that
> the issues are separate, and the charter should describe them as
> such.  This said, there might be work-load- or work-scope-specific
> reasons that suggest splitting the work into separate working
> groups, like those brought up by Lars, Sam, and Scott.  Those
> arguments should be discussed as well.

Exactly.  Thanks.
_______________________________________________
mif mailing list
mif@xxxxxxxx
https://www.ietf.org/mailman/listinfo/mif

---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.
_______________________________________________

Ietf@xxxxxxxx
https://www.ietf.org/mailman/listinfo/ietf

[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Fedora Users]