|Thread Links||Date Links|
|Thread Prev||Thread Next||Thread Index||Date Prev||Date Next||Date Index|
A few comments with [Yan].
My comments in line with [pat] tag
On Wed, Feb 3, 2016 at 3:10 PM, Marek Hajduczenia <marek.hajduczenia@xxxxxxxxx> wrote:
Thank you George.
Inline as well, in red, with [mh0203] tag.
Marek – thanks for taking this up. Some thoughts in response to the questions you ask, inline below. (marked GZ>>>)
As a follow-up from the discussion on YANG models for 802.3 at the last interim session in Atlanta, GA, USA (see http://www.ieee802.org/3/ad_hoc/ngrates/public/16_01/index.html, session #2 for materials), I would like to start email discussion regarding some of the aspects of the future YANG model for IEEE 802.3 interfaces, and specifically the relationship between individual elements from Clause 30, relationship between them, and exposing them in YANG model. Below is the copy of Figure 30-3, which demonstrates relationship between individual managed entities we use for DTE modelling. The list of questions / observations follows:
- The objects oAggregator, oAggregationPort, oAggPortStats and oAggPortDebugInformation are deprecated by IEEE Std 802.1AX-2008. Would it make sense to exclude all LAG-related managed objects from 802.3 YANG model and assume they will be handled by 802.1 when and if 802.1AX-2008 model is created? This would simplify the Ethernet interface model and avoid overlap with potential future 802.1AX work. In the end, 802.1AX model would combine multiple Ethernet interface instances + additional management objects to control the 802.1AX LAG, so I believe we should be fine in this respect.
GZ>>> Completely agree. Deprecating functions means you DON’T DO FURTHER WORK ON THEM. Add to that the bonus that it simplifies the model, and its clear this is the right thing to do. Continuing to evolve a deprecated function is really bad precedent.
[mh0203] Thank you, that also makes sense to me, and if nobody expresses any concerns about my proposed approach, I will work under this assumption going forward, at least to get the initial model created.
- The relationship between oMACEntity and oPHYEntity is 1-to-many, as shown in the figure above. Are there any specific examples of PHYs in 802.3 today where a single MAC entity speaks to multiple PHYs at the same time? What was the original reason to model it in this fashion? I would like to simplify the YANG model by assuming 1:1 relationship for now and I was wondering whether it would be acceptable
GZ>>> I don’t know why the relationships are modeled that way in Clause 30, but Clause 4, which describes the MAC is written entirely from the point of view that it is a 1-to-1 mapping. For example, as far as I can tell, it always refers to “the Physical Layer” and singular transmissions and receptions, never to “a Physical Layer”. Thinking back to the bad old days of CSMA/CD (sure to get a comment from Geoff Thompson on that one J ) handling a 1-to-many MAC-to-PHY mapping would be problematic, and would require additional machinery in the description of Clause 4. Love to hear from some of the early crowd if they understand where and how a multi-PHY MAC fits into Clause 4.
[mh0203] Yes, that is also where I had problems putting things together, and my only thought was about multi-rate PHYs (10/100/1000BASE-T for example), but as far as I understand, they are not described in the standard in this fashion, so the 1:1 mapping would still apply nonetheless.
[pat] The reason it is one to many isn't because many are active at the same time. It is because something that uses auto-negotiation is modeled as having autonegotiation plus all the individual PHYs present even though at most one of the PHYs is active based on the result of negotiation (or configuration). One could alternatively model it as having the PHY capabilities (which belong to autonegotiation) but only one PHY instantiated and therefore only one PHY manageable at any given time. The only reason to do otherwise would be if one needed to configure the inactive PHYs or read information from them. I can't recall anything in the PHYs that needs that.
[Yan] Then it should be a 1-1 mapping between MAC and PHY. But we can provide several ‘cases’ for multiple data rates, to the PHY bound with a MAC.
- Managed objects aPhyType and aPhyTypeList provides a long list of PHYs. Is there any interest in having all legacy PHY types supported or we could rather prune the list starting from – say – 100BASE-T onwards and support only newer PHY types?
GZ>>> I think pruning is a good idea, but I wouldn’t prune by age. We have a bunch of PHYs, some of which have been formally deprecated, some of which maybe should be. Some of the old PHYs are still around (take 10BASE-T – it just won’t die). I understood from the presentation at the ECDC, however, there was an automated way to do the YANG translation, so maybe pruning is more work?
[mh0203] Actually, we tried to emphasize that we would not do automated conversion J I guess this message needs to be emphasized more in the future. Automatic conversion does mapping from MIB to YANG, but it leaves plenty of ‘leftovers’ and clean up is then needed, leading to development from scratch being much faster.
My suggestion to start off from 100BASE PHYs was that it is unlikely that vendors would be putting YANG support on very old equipment. I would expect newer products to support it in the future, but not legacy, end-of-life equipment. We will need to draw the line at some point, but what it is – I am open to suggestions.
[pat] I would prune by status of the PHY in the standard, not by age. That is by whether the PHY has the "not recommended for new installations" note. (By "deprecated" I will mean the devices that have this note.) We should keep 10BASE-T in. When we did EEE, there was significant input that people wanted the change that lowered the 10BASE-T power so it is still being implemented. Since it goes into multispeed PHYs, it can still be implemented in a new PHY. I think it is the only 10 Mb/s PHY that is still in the picture so it isn't much burden to include the one PHY. One could also prune out the other deprecated PHYs. 100BASE-T4 isn't used today (and I don't think it ever had significant deployment.) It is deprecated. That the PHYs are deprecated is a pretty easy uniform bar to use in deciding what to include.
- The initial development effort would be focused on properties common to all Ethernet PHYs, while specific extensions to support EFM OAM, PON, etc. will be added later on, by extending base common model
- Is there any interest in modelling repeater (based on Figure 30–4) or midspan (based on Figure 30–5)? These are very simple devices, but at this time I was planning to focus on DTE only (aka Ethernet interface definition)
GZ>>> I think managing all these entities is goodness, but how would you model a midspan from a dot-3 perspective ? (remember, our specs are written single port) Without its own datalink, that question has been elusive.
[mh0203] That is also something that I was wondering, but it might be that we would build a ‘device’ model, extending the existing ‘system’ model. I wonder though what the value is, given that bridges / switches are way more popular these days and for these to work, we just need a generic 802.3 interface model.
[pat] The repeaters have all been deprecated for a long time and aren't in current use. Therefore, we shouldn't include them. There is no point. For midspans, is anyone making a manageable midspan device? If they are currently being made, they probably should be included, but even then, I think they are relatively low priority.@GZ, the existing model, Figure 30-5, models a midspan as a device containing multiple PSEs, not a single port. A PSE could have an Ethernet port to access the management in addition to its PSEs.
[Yan] For a midspan, it doesn’t have data link function, but only powering circuit, while a PSE switch could be managed by YANG for the configuration/monitoring of the powering feature.