How to announce ethernet capabilities in GMPLS

Freek Dijkstra <fdijkstr@science.uva.nl> Wed, 03 May 2006 15:53 UTC

Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FbJfZ-0001R4-4n for ccamp-archive@ietf.org; Wed, 03 May 2006 11:53:41 -0400
Received: from psg.com ([147.28.0.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FbJfY-0005gr-Lu for ccamp-archive@ietf.org; Wed, 03 May 2006 11:53:41 -0400
Received: from majordom by psg.com with local (Exim 4.60 (FreeBSD)) (envelope-from <owner-ccamp@ops.ietf.org>) id 1FbJYJ-000KtH-Dp for ccamp-data@psg.com; Wed, 03 May 2006 15:46:11 +0000
X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on psg.com
X-Spam-Level:
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00 autolearn=ham version=3.1.1
Received: from [145.99.148.35] (helo=mickey.macfreek.nl) by psg.com with esmtp (Exim 4.60 (FreeBSD)) (envelope-from <fdijkstr@science.uva.nl>) id 1FbJYF-000KsG-DE for ccamp@ops.ietf.org; Wed, 03 May 2006 15:46:07 +0000
Received: from [146.50.22.53] (mbp-freek.science.uva.nl [146.50.22.53]) by mickey.macfreek.nl (Postfix) with ESMTP id 601614AAA7 for <ccamp@ops.ietf.org>; Wed, 3 May 2006 17:46:05 +0200 (CEST)
Message-ID: <4458D03D.8020304@science.uva.nl>
Date: Wed, 03 May 2006 17:46:05 +0200
From: Freek Dijkstra <fdijkstr@science.uva.nl>
User-Agent: Mail/News 1.5.0.2 (Macintosh/20060401)
MIME-Version: 1.0
To: ccamp@ops.ietf.org
Subject: How to announce ethernet capabilities in GMPLS
X-Enigmail-Version: 0.94.0.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Sender: owner-ccamp@ops.ietf.org
Precedence: bulk
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793

Hi,

I have a question about GMPLS.

My interest is mostly scientific in nature; and after reading a few
RFC's and internet drafts, I still found no satisfying answer. I may
have overlooked it.

How would you specify the encoding type for a link with IEEE 802.1q VLAN
tags versus a link which can not do that?
And related, how to distinguish between WAN PHY and LAN PHY encoding?

Imagine a small network with 3 or 4 layer 2 switches, with all
interfaces connected to one central photonic cross connect (MEMS
device). In such a case, it is useful to know the above details.


If I'm correct, a Layer 2 switch announces the capabilities of each
interface using a link state advertisement (LSA).

A LSA seems to contain at least
- "LSP encoding type" and
- "switching type".

In all cases, the parameters seem to be "Ethernet" and "L2SC" respectively.

At least draft-papadimitriou-enhanced-lsps-04 explictly says that WAN
PHY and LAN PHY both fall in the Ethernet "LSP Encoding Type".

draft-dimitri-gels-framework-00 seems to suggest that perhaps new
encoding types must be invented. I take it that I misunderstood, and
this will be defined in the "Switching Capability-Specific Information"
part of the LSA.

I tried looking, and Adrian's excellent Internet and it's protocols
lists that the "Switching Capability-Specific Information" for L2SC
only lists "minimum bandwidth" and "MTU".

Am I correct that the GELS working group will look into extensions for
this purpose? I'm currently not interested (yet) in the specific
details, but mostly in the general idea here. Is there by any chance a
list of already defined "Switching Capability-Specific Information"
parameters for other layers? Perhaps a list of internet drafts to go
through.

I might be wrong here somewhere -- somehow WAN/LAN PHY and IEEE 802.1q
VLAN or not capable seem other type of parameters to me then "MTU"
(which is currently defined for L2SC). If so -- what am I missing?

Regards,
Freek