|
|
|
Jeroen van der Ham: 11/30/2012 7:57 AM EST
|
| |
Action: |
Update
Closed set to 11/30/2012
Status changed from Last Call to Completed
|
|
|
Jason Zurawski: 08/16/2012 7:33 AM EDT
|
| |
Comment: |
no additional comments - close it.
|
| |
Action: |
Update
|
|
|
Freek Dijkstra: 08/08/2012 9:18 AM EDT
|
| |
Action: |
Update
Category changed from – Link / Path / Segment to Technology Extension
|
|
|
Freek Dijkstra: 07/11/2012 8:13 PM EDT
|
| |
Action: |
Update
Status changed from Need proposal to Last Call
|
|
|
Freek Dijkstra: 03/29/2012 12:30 PM EDT
|
| |
Comment: |
I think this proposal also allows the description of unidirected links, as described in artf6533.
Chin asked if it would be possible to describe the "noReturnTraffic" in a switch rather than as part of a subnet, since that is where that logic is
implemented. Freek will provide an example for reference.
|
| |
Action: |
Update
Status changed from Under discussion to Need proposal
|
|
|
Freek Dijkstra: 03/28/2012 10:47 AM EDT
|
| |
Action: |
Update
Category changed from Procedural to – Link / Path / Segment
Status changed from New to Under discussion
|
|
|
Jason Zurawski: 03/28/2012 9:41 AM EDT
|
| |
Comment: |
This proposal is fine by me
|
| |
Action: |
Update
|
|
|
Freek Dijkstra: 03/28/2012 9:09 AM EDT
|
| |
Comment: |
I used the isSource/isSink relation rather than the hasSource/hasSink relation. Not very convenient in this case :)
|
| |
Action: |
Update
|
|
|
Freek Dijkstra: 03/28/2012 9:08 AM EDT
|
| |
Comment: |
Full proposal:
VLAN
====
> * VLAN is a link with multiple source and multiple sink ports,
> and optional parameter noReturnTraffic
> https://forge.ogf.org/sf/go/artf6503
> https://forge.ogf.org/sf/go/artf6542 (duplicate)
> https://forge.ogf.org/svn/repos/nml-examples/201203-vlans/vlan-link.xml
Summary: We want to describe a LAN (or VLAN) between Nodes
Proposal: Use a single Link object, with multiple sources and sinks, and an optional parameter "noReturnTraffic" to signify that
Rationale: A LAN is basically a broadcast domain, with multiple Ports. The "noReturnTraffic" is an optimisation in present (switched) networks, and
seems the easiest way to describe the special case that no traffic flows back to it's source, like it used to in a old LAN with HUBs. The idea to put
this in parameters comes from OGF 33:
https://forge.ogf.org/svn/repos/nml-examples/201109-switchservice/2vlans_option1.xml
Example:
<nml:Port id="urn:ogf:network:example.net:2012:PortAsrc">
<nml:Relation type="isSource">
<nml:Link idRef="urn:ogf:network:example.net:2012:VLAN42"/>
</nml:Relation>
</nml:Port>
<nml:Port id="urn:ogf:network:example.net:2012:PortAsink">
<nml:Relation type="isSink">
<nml:Link idRef="urn:ogf:network:example.net:2012:VLAN42"/>
</nml:Relation>
</nml:Port>
<nml:Port id="urn:ogf:network:example.net:2012:PortBsrc">
<nml:Relation type="isSource">
<nml:Link idRef="urn:ogf:network:example.net:2012:VLAN42"/>
</nml:Relation>
</nml:Port>
<nml:Port id="urn:ogf:network:example.net:2012:PortBsink">
<nml:Relation type="isSink">
<nml:Link idRef="urn:ogf:network:example.net:2012:VLAN42"/>
</nml:Relation>
</nml:Port>
<nml:Port id="urn:ogf:network:example.net:2012:PortCsrc">
<nml:Relation type="isSource">
<nml:Link idRef="urn:ogf:network:example.net:2012:VLAN42"/>
</nml:Relation>
</nml:Port>
<nml:Port id="urn:ogf:network:example.net:2012:PortCsink">
<nml:Relation type="isSink">
<nml:Link idRef="urn:ogf:network:example.net:2012:VLAN42"/>
</nml:Relation>
</nml:Port>
<nml:Link idRef="urn:ogf:network:example.net:2012:VLAN42">
<nml:name>VLAN 42</nml:name>
<nml:parameter name="noReturnTraffic">true</nml:parameter>
</nml:Link>
Note: the concept of using a nml:parameter is in-scope of this proposal. The exact XML representation of the nml:parameter is out-of-scope, and may be
discussed later, if the WG prefers so.
|
| |
Action: |
Update
|
|
|
Freek Dijkstra: 03/28/2012 8:57 AM EDT
|
| |
Comment: |
This is a duplicate of artf6503. I closed that one because it has even fewer comments.
|
| |
Action: |
Update
|
|
|
Jason Zurawski: 03/27/2012 7:43 PM EDT
|
| |
Comment: |
This issue should be updated with the discussion from the mailing list
|
| |
Action: |
Update
|
|
|
|
