On Wed, Sep 12, 2018 at 7:42 PM, Brian E Carpenter
wrote:
> Just picking on one part of Tom's excellent note:
>
> On 2018-09-13 11:14, Tom Herbert wrote:
> ...
>> IMO, IETF's strength and advantage is that it focuses on standardizing
>> protocols without standardizing network architecture. This pr
Just picking on one part of Tom's excellent note:
On 2018-09-13 11:14, Tom Herbert wrote:
> IMO, IETF's strength and advantage is that it focuses on standardizing
> protocols without standardizing network architecture. This provides
> all the necessary freedom for to build networks as appropr
On 2018-09-13 03:50, Tom Herbert wrote:
> On Wed, Sep 12, 2018 at 5:39 PM, Amelia Andersdotter
> wrote:
>> Dear all,
>>
>> Thanks Brian for going through all this work, and Tom and Alexandre for
>> providing interesting feedback.
>>
>> In section 3, it may be more interesting to divide Examples of
On Wed, Sep 12, 2018 at 5:39 PM, Amelia Andersdotter
wrote:
> Dear all,
>
> Thanks Brian for going through all this work, and Tom and Alexandre for
> providing interesting feedback.
>
> In section 3, it may be more interesting to divide Examples of Limited
> Domain Requirements into networks conta
Dear all,
Thanks Brian for going through all this work, and Tom and Alexandre for
providing interesting feedback.
In section 3, it may be more interesting to divide Examples of Limited
Domain Requirements into networks containing human end-users and
networks that don't contain human end-users (su
On Wed, Sep 12, 2018 at 1:53 PM, Brian E Carpenter
wrote:
> Tom,
>
> On 2018-09-13 04:10, Tom Herbert wrote:
>> Hi Brian,
>>
>> Thanks for the draft!
>>
>> I am still concerned about the implications and perceptions this draft
>> might entail. Particularly, I wonder whether this will fracture the
Tom,
On 2018-09-13 04:10, Tom Herbert wrote:
> Hi Brian,
>
> Thanks for the draft!
>
> I am still concerned about the implications and perceptions this draft
> might entail. Particularly, I wonder whether this will fracture the
> Internet (even more) and encourage (even more) protocol ossificati
Andy, and Alex,
Yes. I think we need to say more about this aspect. It's clear that
a technology boundary is a kind of "natural" domain boundary,
but on the other hand we've been overcoming such boundaries for
many years (anybody remember Ethernets bridged together over FDDI?).
And of course VLANs
Alex and Brian,
Any time you have a limited domain layer 2 network (such as a campus
Ethernet, or more application-specific networks like Alex was mentioning),
one thing that commonly occurs is that people want to use tunnels to
interconnect such networks either over the Internet, or alternatively
Hi Brian,
Thanks for the draft!
I am still concerned about the implications and perceptions this draft
might entail. Particularly, I wonder whether this will fracture the
Internet (even more) and encourage (even more) protocol ossification
by allowing developers and protocol designers to take sho
I read the draft. I find it describes well a state of matters in
networking along a Limited Domain paradigm.
Maybe some call IP-enabled Limited Domains 'walled gardens'.
4. Examples of Limited Domain Solutions
This section lists various examples of specific limited domain
solutions th
11 matches
Mail list logo
