RE: [imss] Last Call comments on draft-ietf-imss-fc-zs-mib-00.txt

> OK, I assume you're not suggesting a re-ordering, but just the
insertion
> of sub-section titles, e.g., insert "3.3  Zoning Configuration and
> Management" immediately before::
> 
>    Zones are configured via a Fabric Zone Server, using ...

Yes.

Thanks,
--David

> -----Original Message-----
> From: Keith McCloghrie [mailto:kzm@cisco.com] 
> Sent: Thursday, September 14, 2006 12:03 PM
> To: Black, David
> Cc: imss@ietf.org
> Subject: Re: [imss] Last Call comments on 
> draft-ietf-imss-fc-zs-mib-00.txt
> 
> > Section 3 is not a "Short" Overview of Fibre Channel ;-).  It could
> 
> OK, I'll just delete the "Short".
> 
> > usefully be broken into 3 subsections:
> > - Overview
> 
> After deleting "Short", this would be better as "Introduction" or as
> "General Overview".
> 
> > - Zoning
> > - Zoning Configuration and Management
> 
> OK, I assume you're not suggesting a re-ordering, but just the
insertion
> of sub-section titles, e.g., insert "3.3  Zoning Configuration and
> Management" immediately before::
> 
>    Zones are configured via a Fabric Zone Server, using ...
>  
> > The first paragraph describing zoning says:
> > 
> >    Zones within a fabric provide a mechanism to control frame
delivery
> >    between Nx_Ports ("Hard Zoning") or to expose selected views of
Name
> >    Server information ("Soft Zoning").  This technique is similar to
> >    virtual private networks in that the fabric has the ability to
group
> >    devices into Zones.
> > 
> > It needs an additional few sentences to explain what a zone does and
> > where it's enforced, specifically to make the following points:
> > - Communication is only possible when the communicating endpoints
> > 	are members of a common zone.
> > - Hard zoning and soft zoning are two different means of realizing
> > 	this.  Hard zoning is enforced in the fabric (i.e., switches)
> > 	whereas soft zoning is enforced at the endpoints (e.g., HBAs)
> > 	by relying on the endpoints to not send traffic to an N_Port_ID
> > 	not obtained from the nameserver with a few exceptions for well
> > 	known N_Port_IDs used to bootstrap the fabric (e.g., talk to the
> > 	nameserver).
>  
> OK.
> 
> > Section 5.4 ought to explain how an SNMP management client can
determine
> > whether a fabric is operating in basic vs. enhanced mode.
>  
> OK.  I'll add a paragraph which mentions t11ZsServerOperationMode, and
> probably t11ZsServerCapabilityObject as well.
> 
> Keith.
> 

_______________________________________________
imss mailing list
imss@ietf.org
https://www1.ietf.org/mailman/listinfo/imss