Substrate Resouces

[John Jacob-2]

All,

Attached is an excel list of substrate components and resources. One of
our near term objectives is to agree on a list of substrate resources
and identify the ability to slice or program these as well as classify
them as physical, logical or synthetic. Challenges and limitations
should also be captured. This list will help the substrate working group
in defining the substrate architecture and identifying risks. The
attached list is a starting point and is intended to initiate discussion
in this area. Please reply to the substrate-wg mailing list with your
input and I will maintain a master copy of the spread sheet.

Note: This list needs basic input regarding wireless networks.

-John

---------------------------------------------------------------------
John Jacob
Substrate Working Group Systems Engineer
BBN Technologies
10 Moulton St
Cambridge, MA 02138
[phone]


_______________________________________________
substrate-wg mailing list
substrate-wg@...
http://lists.geni.net/mailman/listinfo/substrate-wg

[Jay Lepreau]

On sheet2, do columns C,D,E correspond to the Physical, Logical, and Synthetic
classes of resources you outline at the bottom?

And I guess that col A is "Substrate" and B is "Component"
that you outline below?

_______________________________________________
substrate-wg mailing list
substrate-wg@...
http://lists.geni.net/mailman/listinfo/substrate-wg

[Masanori Takashima]

Hi, John,

Let me know what do you mean by Sliceable at column F.

I guess that Sliceable means that whatever an entry in column B consists
of a set of finer grained resources. For example, CPU is Sliceable
because CPU consists of a set of CPU usage, where CPU usage is a
resource.

Best regards,
Masanori



_______________________________________________
substrate-wg mailing list
substrate-wg@...
http://lists.geni.net/mailman/listinfo/substrate-wg

[stuart.d.elby]

John,

I have the same question; I am not sure what the boundary is between
physical and logical as a result of sliceability.  Building on
Masanori's example, ff a network element has a CPU running routing
protocol stacks and those processing threads can be partitioned into
virtual router threads, then I have the basis for virtual routing
functions (VRFs) which are logical routers built by 'slicing' a physical
CPU. Is this what you were thinking when you labeled the columns?

Another observation is that you have labeled 'Ports' as logical
constructs.  I do agree that this is a very important type of port we
need to consider, but let's not loose sight of the physical (e.g. 100G)
ports that will be used to connect these platforms to the underlying
fiber facilities. I suggest that we consider "line cards" and "switch
ports" physical entities, and "logical (switch) ports" logical entities
to avoid confusion. The physical binding of a switch port "a" to a fiber
facility to a switch port "b" would be a "physical circuit" or
"connection". All other bindings of logical ports would be "synthetic"
paths as you have already defined.

-Stu

-----Original Message-----
From: substrate-wg-bounces@...
[mailto:substrate-wg-bounces@...] On Behalf Of Masanori Takashima
Sent: Friday, November 02, 2007 12:57 AM
To: John Jacob
Cc: substrate-wg@...
Subject: Re: [substrate-wg] Substrate Resouces

Hi, John,

Let me know what do you mean by Sliceable at column F.

I guess that Sliceable means that whatever an entry in column B consists
of a set of finer grained resources. For example, CPU is Sliceable
because CPU consists of a set of CPU usage, where CPU usage is a
resource.

Best regards,
Masanori



_______________________________________________
substrate-wg mailing list
substrate-wg@...
http://lists.geni.net/mailman/listinfo/substrate-wg

_______________________________________________
substrate-wg mailing list
substrate-wg@...
http://lists.geni.net/mailman/listinfo/substrate-wg

[John Jacob-2]

Jay,

I am somewhat confused on the difference between substrate and
component.  Column A is  a list of components (routers, switches, DWDM  
transport) etc.,  and  Column B is the associated resources  (bandwidth,
wavelength),
Columns C-E are used to specify the resource in Column B as physical,
logical, synthetic.

If this is not the correct use of these terms, please let me know and I
will make corrections.

John  



Jay Lepreau wrote:
> On sheet2, do columns C,D,E correspond to the Physical, Logical, and Synthetic
> classes of resources you outline at the bottom?
>
> And I guess that col A is "Substrate" and B is "Component"
> that you outline below?
>
>  


_______________________________________________
substrate-wg mailing list
substrate-wg@...
http://lists.geni.net/mailman/listinfo/substrate-wg

[John Jacob-2]

Stu,

You made some good points and raised good questions. I would like to
know how others on this list feel about this. As a point of
clarification, the selection of physical/logical/synthetic in the
current version was primarily to stimulate discussion. It is quite
likely that several of these assignments are confusing or incorrect. I
will incorporate your input into the master version to be redistributed
after the initial wave of discussions.

Thanks,
John



stuart.d.elby@... wrote:

> John,
>
> I have the same question; I am not sure what the boundary is between
> physical and logical as a result of sliceability.  Building on
> Masanori's example, ff a network element has a CPU running routing
> protocol stacks and those processing threads can be partitioned into
> virtual router threads, then I have the basis for virtual routing
> functions (VRFs) which are logical routers built by 'slicing' a physical
> CPU. Is this what you were thinking when you labeled the columns?
>
> Another observation is that you have labeled 'Ports' as logical
> constructs.  I do agree that this is a very important type of port we
> need to consider, but let's not loose sight of the physical (e.g. 100G)
> ports that will be used to connect these platforms to the underlying
> fiber facilities. I suggest that we consider "line cards" and "switch
> ports" physical entities, and "logical (switch) ports" logical entities
> to avoid confusion. The physical binding of a switch port "a" to a fiber
> facility to a switch port "b" would be a "physical circuit" or
> "connection". All other bindings of logical ports would be "synthetic"
> paths as you have already defined.
>
> -Stu
>
> -----Original Message-----
> From: substrate-wg-bounces@...
> [mailto:substrate-wg-bounces@...] On Behalf Of Masanori Takashima
> Sent: Friday, November 02, 2007 12:57 AM
> To: John Jacob
> Cc: substrate-wg@...
> Subject: Re: [substrate-wg] Substrate Resouces
>
> Hi, John,
>
> Let me know what do you mean by Sliceable at column F.
>
> I guess that Sliceable means that whatever an entry in column B consists
> of a set of finer grained resources. For example, CPU is Sliceable
> because CPU consists of a set of CPU usage, where CPU usage is a
> resource.
>
> Best regards,
> Masanori
>
>
>
> _______________________________________________
> substrate-wg mailing list
> substrate-wg@...
> http://lists.geni.net/mailman/listinfo/substrate-wg
>
>  

_______________________________________________
substrate-wg mailing list
substrate-wg@...
http://lists.geni.net/mailman/listinfo/substrate-wg

[Keren Bergman]

 
John,

I agree with Stu's comments. Perhaps we can define a "link" physical
component that includes resources such as 100G. This would enable
construction of (sub)-networks from the available components and their
resources - to the extent that these resources can be partitioned. I would
argue to take out the "network" component since it's a higher level entity -
it should be possible to build it from the components we define. The
resources (restoration, protection, QoS, etc.) can be provided via the
components.

Best,

Keren

-----Original Message-----
From: substrate-wg-bounces@... [mailto:substrate-wg-bounces@...]
On Behalf Of John Jacob
Sent: Friday, November 02, 2007 8:38 AM
To: substrate-wg@...
Subject: Re: [substrate-wg] Substrate Resouces

Stu,

You made some good points and raised good questions. I would like to know
how others on this list feel about this. As a point of clarification, the
selection of physical/logical/synthetic in the current version was primarily
to stimulate discussion. It is quite likely that several of these
assignments are confusing or incorrect. I will incorporate your input into
the master version to be redistributed after the initial wave of
discussions.

Thanks,
John


stuart.d.elby@... wrote:

> John,
>
> I have the same question; I am not sure what the boundary is between
> physical and logical as a result of sliceability.  Building on
> Masanori's example, ff a network element has a CPU running routing
> protocol stacks and those processing threads can be partitioned into
> virtual router threads, then I have the basis for virtual routing
> functions (VRFs) which are logical routers built by 'slicing' a
> physical CPU. Is this what you were thinking when you labeled the columns?
>
> Another observation is that you have labeled 'Ports' as logical
> constructs.  I do agree that this is a very important type of port we
> need to consider, but let's not loose sight of the physical (e.g.
> 100G) ports that will be used to connect these platforms to the
> underlying fiber facilities. I suggest that we consider "line cards"
> and "switch ports" physical entities, and "logical (switch) ports"
> logical entities to avoid confusion. The physical binding of a switch
> port "a" to a fiber facility to a switch port "b" would be a "physical
> circuit" or "connection". All other bindings of logical ports would be

"synthetic"

> paths as you have already defined.
>
> -Stu
>
> -----Original Message-----
> From: substrate-wg-bounces@...
> [mailto:substrate-wg-bounces@...] On Behalf Of Masanori Takashima
> Sent: Friday, November 02, 2007 12:57 AM
> To: John Jacob
> Cc: substrate-wg@...
> Subject: Re: [substrate-wg] Substrate Resouces
>
> Hi, John,
>
> Let me know what do you mean by Sliceable at column F.
>
> I guess that Sliceable means that whatever an entry in column B
> consists of a set of finer grained resources. For example, CPU is
> Sliceable because CPU consists of a set of CPU usage, where CPU usage
> is a resource.
>
> Best regards,
> Masanori
>
>
>
> _______________________________________________
> substrate-wg mailing list
> substrate-wg@...
> http://lists.geni.net/mailman/listinfo/substrate-wg
>
>  

_______________________________________________
substrate-wg mailing list
substrate-wg@...
http://lists.geni.net/mailman/listinfo/substrate-wg


_______________________________________________
substrate-wg mailing list
substrate-wg@...
http://lists.geni.net/mailman/listinfo/substrate-wg

[Hongwei Zhang]

Hi John,

Please find attached a file that contains the few components/resources that I feel relevant to the "wireless sensor networks" substrate.

Best,

Hongwei
---
http://www.cs.wayne.edu/~hzhang/


John Jacob wrote:

All,

Attached is an excel list of substrate components and resources. One of our near term objectives is to agree on a list of substrate resources and identify the ability to slice or program these as well as classify them as physical, logical or synthetic. Challenges and limitations should also be captured. This list will help the substrate working group in defining the substrate architecture and identifying risks. The attached list is a starting point and is intended to initiate discussion in this area. Please reply to the substrate-wg mailing list with your input and I will maintain a master copy of the spread sheet.

Note: This list needs basic input regarding wireless networks.

-John

---------------------------------------------------------------------
John Jacob
Substrate Working Group Systems Engineer
BBN Technologies
10 Moulton St
Cambridge, MA 02138
[phone]

_______________________________________________
substrate-wg mailing list
substrate-wg@...
http://lists.geni.net/mailman/listinfo/substrate-wg

_______________________________________________
substrate-wg mailing list
substrate-wg@...
http://lists.geni.net/mailman/listinfo/substrate-wg

[Drew Perkins]

Some parts of this message have been removed. Learn more about Nabble's security policy.

Perhaps I’m a bit confused by the word “sliceable”, but my sense is that this word is interchangeable with “multiplexable”. If so, then there are several ways of multiplexing a resource. When it comes to CPUs, we think of time division multiplexing to get virtual CPUs. When it comes to fibers, I think we can think of not only time division multiplexing (TDM) but also frequency/wavelength division multiplexing (FDM/WDM) and space division multiplexing (SDM). A simple example of SDM is that we might partition the network into multiple pieces for use by multiple experiments. These partitions may be dynamic based on what experiments are being run at any time. Am I off in the weeds?

 

Drew

 

 

 

 

Drew Perkins

Chief Technology Officer

 

Infinera Corporation

169 Java Drive

Sunnyvale, CA, 94089

 

Direct:  [phone]

Fax:     [phone]

Mobile: [phone]

dperkins@...

http://www.infinera.com

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

-----Original Message-----
From: substrate-wg-bounces@... [mailto:substrate-wg-bounces@...] On Behalf Of John Jacob
Sent: Friday, November 02, 2007 6:38 AM
To: substrate-wg@...
Subject: Re: [substrate-wg] Substrate Resouces

 

Stu,

 

You made some good points and raised good questions. I would like to

know how others on this list feel about this. As a point of

clarification, the selection of physical/logical/synthetic in the

current version was primarily to stimulate discussion. It is quite

likely that several of these assignments are confusing or incorrect. I

will incorporate your input into the master version to be redistributed

after the initial wave of discussions.

 

Thanks,

John

 

 

 

stuart.d.elby@... wrote:

> John,

> 

> I have the same question; I am not sure what the boundary is between

> physical and logical as a result of sliceability.  Building on

> Masanori's example, ff a network element has a CPU running routing

> protocol stacks and those processing threads can be partitioned into

> virtual router threads, then I have the basis for virtual routing

> functions (VRFs) which are logical routers built by 'slicing' a physical

> CPU. Is this what you were thinking when you labeled the columns?

> 

> Another observation is that you have labeled 'Ports' as logical

> constructs.  I do agree that this is a very important type of port we

> need to consider, but let's not loose sight of the physical (e.g. 100G)

> ports that will be used to connect these platforms to the underlying

> fiber facilities. I suggest that we consider "line cards" and "switch

> ports" physical entities, and "logical (switch) ports" logical entities

> to avoid confusion. The physical binding of a switch port "a" to a fiber

> facility to a switch port "b" would be a "physical circuit" or

> "connection". All other bindings of logical ports would be "synthetic"

> paths as you have already defined.

> 

> -Stu

> 

> -----Original Message-----

> From: substrate-wg-bounces@...

> [mailto:substrate-wg-bounces@...] On Behalf Of Masanori Takashima

> Sent: Friday, November 02, 2007 12:57 AM

> To: John Jacob

> Cc: substrate-wg@...

> Subject: Re: [substrate-wg] Substrate Resouces

> 

> Hi, John,

> 

> Let me know what do you mean by Sliceable at column F.

> 

> I guess that Sliceable means that whatever an entry in column B consists

> of a set of finer grained resources. For example, CPU is Sliceable

> because CPU consists of a set of CPU usage, where CPU usage is a

> resource.

> 

> Best regards,

> Masanori

> 

> 

> 

> _______________________________________________

> substrate-wg mailing list

> substrate-wg@...

> http://lists.geni.net/mailman/listinfo/substrate-wg

> 

>  

 

 

_______________________________________________

substrate-wg mailing list

substrate-wg@...

http://lists.geni.net/mailman/listinfo/substrate-wg

_______________________________________________
substrate-wg mailing list
substrate-wg@...
http://lists.geni.net/mailman/listinfo/substrate-wg

[Hongwei Zhang]

Hi John,

I think I missed a very important resource for a "wireless sensor node" component --- sensor --- in my last email. Please find attached an updated version of the file with "sensor" included.

Best,

Hongwei
---
http://www.cs.wayne.edu/~hzhang/


Hongwei Zhang wrote:

Hi John,

Please find attached a file that contains the few components/resources that I feel relevant to the "wireless sensor networks" substrate.

Best,

Hongwei
---
http://www.cs.wayne.edu/~hzhang/


John Jacob wrote:

All,

Attached is an excel list of substrate components and resources. One of our near term objectives is to agree on a list of substrate resources and identify the ability to slice or program these as well as classify them as physical, logical or synthetic. Challenges and limitations should also be captured. This list will help the substrate working group in defining the substrate architecture and identifying risks. The attached list is a starting point and is intended to initiate discussion in this area. Please reply to the substrate-wg mailing list with your input and I will maintain a master copy of the spread sheet.

Note: This list needs basic input regarding wireless networks.

-John

---------------------------------------------------------------------
John Jacob
Substrate Working Group Systems Engineer
BBN Technologies
10 Moulton St
Cambridge, MA 02138
[phone]

_______________________________________________
substrate-wg mailing list
substrate-wg@...
http://lists.geni.net/mailman/listinfo/substrate-wg

_______________________________________________
substrate-wg mailing list
substrate-wg@...
http://lists.geni.net/mailman/listinfo/substrate-wg

_______________________________________________
substrate-wg mailing list
substrate-wg@...
http://lists.geni.net/mailman/listinfo/substrate-wg

[Peter Steenkiste]

A couple of comments, mostly about the structure:

Following up on Jay's comment, it looks like Column A has a mixture of
what I think of as substrates (e.g. a network) and components (e.g. a
switch or optical line).

It is not clear that the three level hierarchy (substrate - component -
resource) will always be sufficient. For example, we will have computing
devices (including CPU, memory, etc. resources) in switches, computing
clusters, etc.  So at least it looks like components  can be part of
larger components?  The people working on resource descriptors probably
know a lot more about this already.

It would be useful to clarify what it means to have an "X" in the
sliceable and programmable column.  Does it mean that this resource will
always be sl/pr or that it will sometimes be sl/pr (i.e. some instances
will be and others will not). I assume it is the latter?

It is also possible to emulate (certain aspects of) a network (I am
mostly familiar with this in wireless).  Should such emulated networks
be listed as a separate type of resource or substrate?  Alternatively,
they could be viewed as simply instances of the non-emulated substrate
or component (i.e. it is a more programmable version).  The former seems
cleaner, but it will drive up the number of rows.  This is of course
related to the previous paragraph.

Peter



Jay Lepreau wrote:

> On sheet2, do columns C,D,E correspond to the Physical, Logical, and Synthetic
> classes of resources you outline at the bottom?
>
> And I guess that col A is "Substrate" and B is "Component"
> that you outline below?
>
> _______________________________________________
> substrate-wg mailing list
> substrate-wg@...
> http://lists.geni.net/mailman/listinfo/substrate-wg
>

_______________________________________________
substrate-wg mailing list
substrate-wg@...
http://lists.geni.net/mailman/listinfo/substrate-wg

[John Jacob-2]

Keren,

This is a good suggestion, but it raises some questions.  Besides
bandwidth, what other resources are attributed to the link-component?
Should we include the end-node sites as a link resource? How would this
be different than reserving bandwidth on specific nodes, e.g. "I want ?
Gbps  connecting the set of  {a1...an}  switches.

John



Keren Bergman wrote:

>  
> John,
>
> I agree with Stu's comments. Perhaps we can define a "link" physical
> component that includes resources such as 100G. This would enable
> construction of (sub)-networks from the available components and their
> resources - to the extent that these resources can be partitioned. I would
> argue to take out the "network" component since it's a higher level entity -
> it should be possible to build it from the components we define. The
> resources (restoration, protection, QoS, etc.) can be provided via the
> components.
>
> Best,
>
> Keren
>
> -----Original Message-----
> From: substrate-wg-bounces@... [mailto:substrate-wg-bounces@...]
> On Behalf Of John Jacob
> Sent: Friday, November 02, 2007 8:38 AM
> To: substrate-wg@...
> Subject: Re: [substrate-wg] Substrate Resouces
>
> Stu,
>
> You made some good points and raised good questions. I would like to know
> how others on this list feel about this. As a point of clarification, the
> selection of physical/logical/synthetic in the current version was primarily
> to stimulate discussion. It is quite likely that several of these
> assignments are confusing or incorrect. I will incorporate your input into
> the master version to be redistributed after the initial wave of
> discussions.
>
> Thanks,
> John
>
>
> stuart.d.elby@... wrote:
>  
>> John,
>>
>> I have the same question; I am not sure what the boundary is between
>> physical and logical as a result of sliceability.  Building on
>> Masanori's example, ff a network element has a CPU running routing
>> protocol stacks and those processing threads can be partitioned into
>> virtual router threads, then I have the basis for virtual routing
>> functions (VRFs) which are logical routers built by 'slicing' a
>> physical CPU. Is this what you were thinking when you labeled the columns?
>>
>> Another observation is that you have labeled 'Ports' as logical
>> constructs.  I do agree that this is a very important type of port we
>> need to consider, but let's not loose sight of the physical (e.g.
>> 100G) ports that will be used to connect these platforms to the
>> underlying fiber facilities. I suggest that we consider "line cards"
>> and "switch ports" physical entities, and "logical (switch) ports"
>> logical entities to avoid confusion. The physical binding of a switch
>> port "a" to a fiber facility to a switch port "b" would be a "physical
>> circuit" or "connection". All other bindings of logical ports would be
>>    
> "synthetic"
>  
>> paths as you have already defined.
>>
>> -Stu
>>
>> -----Original Message-----
>> From: substrate-wg-bounces@...
>> [mailto:substrate-wg-bounces@...] On Behalf Of Masanori Takashima
>> Sent: Friday, November 02, 2007 12:57 AM
>> To: John Jacob
>> Cc: substrate-wg@...
>> Subject: Re: [substrate-wg] Substrate Resouces
>>
>> Hi, John,
>>
>> Let me know what do you mean by Sliceable at column F.
>>
>> I guess that Sliceable means that whatever an entry in column B
>> consists of a set of finer grained resources. For example, CPU is
>> Sliceable because CPU consists of a set of CPU usage, where CPU usage
>> is a resource.
>>
>> Best regards,
>> Masanori
>>
>>
>>
>> _______________________________________________
>> substrate-wg mailing list
>> substrate-wg@...
>> http://lists.geni.net/mailman/listinfo/substrate-wg
>>
>>  
>>    
>
>
> _______________________________________________
> substrate-wg mailing list
> substrate-wg@...
> http://lists.geni.net/mailman/listinfo/substrate-wg
>
>
> _______________________________________________
> substrate-wg mailing list
> substrate-wg@...
> http://lists.geni.net/mailman/listinfo/substrate-wg
>
>  

_______________________________________________
substrate-wg mailing list
substrate-wg@...
http://lists.geni.net/mailman/listinfo/substrate-wg

[John Jacob-2]

Drew,

I think all of these examples are within the meaning of "creating a
slice". We should try to maintain a consistent language with the GENI
architecture folks, which use slice as an experiment built from a
collection component resource slivers....I led us off path with
sliceable in this worksheet, so I will correct that. A sliver being a
"multiplexable" unit, in some instances. I also agree that the
partitioning is dynamic and experiment dependent.

John


Drew Perkins wrote:

>
> Perhaps I’m a bit confused by the word “sliceable”, but my sense is
> that this word is interchangeable with “multiplexable”. If so, then
> there are several ways of multiplexing a resource. When it comes to
> CPUs, we think of time division multiplexing to get virtual CPUs. When
> it comes to fibers, I think we can think of not only time division
> multiplexing (TDM) but also frequency/wavelength division multiplexing
> (FDM/WDM) and space division multiplexing (SDM). A simple example of
> SDM is that we might partition the network into multiple pieces for
> use by multiple experiments. These partitions may be dynamic based on
> what experiments are being run at any time. Am I off in the weeds?
>
> Drew
>
> cid:image001.jpg@...
>
> Drew Perkins
>
> Chief Technology Officer
>
> Infinera Corporation
>
> 169 Java Drive
>
> Sunnyvale, CA, 94089
>
> Direct: [phone]
>
> Fax: [phone]
>
> Mobile: [phone]
>
> dperkins@... <mailto:dperkins@...>
>
> http://www.infinera.com <http://www.infinera.com/>
>
> -----Original Message-----
> From: substrate-wg-bounces@...
> [mailto:substrate-wg-bounces@...] On Behalf Of John Jacob
> Sent: Friday, November 02, 2007 6:38 AM
> To: substrate-wg@...
> Subject: Re: [substrate-wg] Substrate Resouces
>
> Stu,
>
> You made some good points and raised good questions. I would like to
>
> know how others on this list feel about this. As a point of
>
> clarification, the selection of physical/logical/synthetic in the
>
> current version was primarily to stimulate discussion. It is quite
>
> likely that several of these assignments are confusing or incorrect. I
>
> will incorporate your input into the master version to be redistributed
>
> after the initial wave of discussions.
>
> Thanks,
>
> John
>
> stuart.d.elby@... wrote:
>
> > John,
>
> >
>
> > I have the same question; I am not sure what the boundary is between
>
> > physical and logical as a result of sliceability. Building on
>
> > Masanori's example, ff a network element has a CPU running routing
>
> > protocol stacks and those processing threads can be partitioned into
>
> > virtual router threads, then I have the basis for virtual routing
>
> > functions (VRFs) which are logical routers built by 'slicing' a physical
>
> > CPU. Is this what you were thinking when you labeled the columns?
>
> >
>
> > Another observation is that you have labeled 'Ports' as logical
>
> > constructs. I do agree that this is a very important type of port we
>
> > need to consider, but let's not loose sight of the physical (e.g. 100G)
>
> > ports that will be used to connect these platforms to the underlying
>
> > fiber facilities. I suggest that we consider "line cards" and "switch
>
> > ports" physical entities, and "logical (switch) ports" logical entities
>
> > to avoid confusion. The physical binding of a switch port "a" to a fiber
>
> > facility to a switch port "b" would be a "physical circuit" or
>
> > "connection". All other bindings of logical ports would be "synthetic"
>
> > paths as you have already defined.
>
> >
>
> > -Stu
>
> >
>
> > -----Original Message-----
>
> > From: substrate-wg-bounces@...
>
> > [mailto:substrate-wg-bounces@...] On Behalf Of Masanori Takashima
>
> > Sent: Friday, November 02, 2007 12:57 AM
>
> > To: John Jacob
>
> > Cc: substrate-wg@...
>
> > Subject: Re: [substrate-wg] Substrate Resouces
>
> >
>
> > Hi, John,
>
> >
>
> > Let me know what do you mean by Sliceable at column F.
>
> >
>
> > I guess that Sliceable means that whatever an entry in column B consists
>
> > of a set of finer grained res