From: "David Addison" Date: Wed, 15 May 1996 14:46:24 +0100 To: P8021@hepnrc.hep.net Subject: Comments on 802.1p/D3 Tony, here are some initial comments on 802.1p/D3. Page 17 Line 40/41 MANAGER_DEFINE_DEFAULT_FORWARD_WITH_INBOUND_PRIORITY_PRIORITY_MODE There is an extra 'PRIORITY' in this name definition. Page 18 2.6.9.6 Registration range configuration I am not convinced of the usefulness of this feature as it only allows the definition of a single, contiguous range of addresses. Perhaps it should allow multiple, disjoint ranges to be specified ? Also, the range could specify which addresses are *not* allowed for Group registration requests, assuming that this will be the typical usage. Page 18 Line 19 Range definition doesn't seem correct; I think it should be START_ADDRESS <= MAC Address <= END_ADDRESS Page 18 Line 24 Range definition doesn't seem correct; I think it should be END_ADDRESS < MAC Address < START_ADDRESS Page 21 Line 1 Spurious full-stop. Page 28 Line 15 Text does not specify that user_priority can be statically or dynamically defined. Page 32 Line 44 Do not require a 'Port number' parameter as it is a per-bridge operation. Page 33 Line 9 Do not require a 'Port number' parameter as it is a per-bridge operation. Page 33 Line 54 Bullet label a) is repeated. Page 35 Line 9 Database is capitalized. Page 60 Line 37 What is the definition/default value of MinPriority ? Page 61 Line 10 I don't like the non-zero lower bound of the interval definition for T; JoinTime < T < 1.1 * JoinTime as it significantly effects the required resolution of the GARP timer. Page 64 Lines 35-47 These conditions do not make sense. I think line 37 should end; , and any of the following conditions are false: and conditions j), k) and l) need to be negated. i.e. j) If the state machine represents membership registration, the Group Registration Entry contains a statically defined registered_for_membership_on_port_set; k) If the state machine represents existence registration, the Group Registration Entry contains a statically defined registered_for_existence_on_port_set; l) If the Group Registration Entry contains a registration_permitted_on_port_set, the Port concerned is not identified as one of the set of Ports on which Applicants may register. Page 64 Line 51 I think the sentence should end; , and the following conditions are all true: Page 65 Lines 50,51 Does the rLeave event occur if the registrated_for_[membership|existence]_on_port_set is statically defined ? Page 70 Line 5 Sentence is ambiguous. Should read; The reception of any of the three Join All PDU types by a Bridge Port will cause that Port to operate in Filtering Mode 2A. Page 73 Line 11 Page 73 Line 24 Page 73 Line 38 Why is the Delay value non-zero for JoinAll PDUs ? General questions ----------------- I am confused about the behaviour of statically defined group registrations (e.g. a static registered_for_membership_on_port_set). In 9.7.2.2, it seems that Registrar state machines that contain statically defined registration information do not take part in the normal GARP protocol exchanges. Therefore, is static group registration information propagated to other Bridges in the network via the GARP protocol ? Or do all Bridges have to have static information configured for the given Group ? Yours, David. -- David Addison, Hewlett-Packard Laboratories, NTD addy@hplb.hpl.hp.com Filton Road, Stoke Gifford, Bristol, BS12 6QZ Tel: +44 (0)117 922 9543 Fax: +44 (0)117 9228924