Xref: utzoo comp.protocols.iso:1581 comp.dcom.lans:7377
Path: utzoo!utgpu!watserv1!watmath!att!linac!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!rpi!batcomputer!munnari.oz.au!bruce!monu0.cc.monash.edu.au!monu6!ajm
From: ajm@monu6.cc.monash.edu.au (Tony McGregor)
Newsgroups: comp.protocols.iso,comp.dcom.lans
Subject: 8802-2 Use of P_FLAG
Summary: Is this an error in the standard?
Keywords: IEEE 802.2 ISO 8802-2 state transition table
Message-ID: <1991Feb28.031949.25743@monu6.cc.monash.edu.au>
Date: 28 Feb 91 03:19:49 GMT
Organization: Caulfield Campus, Monash University, Melb., Australia.
Lines: 23


I've been reading the ISO 8802-2 Logical Link Control standard and I'm
having a problem understanding the use of the P_FLAG.

Table 7-1 (Connection Component State Transitions) on page 97, Current
state ADM, Event RECEIVE_SABME_CMD(P=X) includes the action P_FLAG:=P.

I assumed that this was so that the UA_RSP sent (if the network layer
accepts the call) could have the F bit set appropriately. However in
state CONN, event CONNECT_RESPONSE, F_FLAG is used to determine the
value of the F bit (action SEND_UA_RSP(F=F_FLAG)).  As far as I can
see the F_FLAG hasn't been set yet.

Is this a misprint or have I missed something. If it is a misprint
which is wrong?

Tony 
----------------------------------------------------------------------
Tony McGregor ( ajm@monu6.cc.monash.edu.au )  
Department of Robotics and Digital Technology, Monash University
PO Box 197, Caulfield East, Vic 3145, Australia  
Phone: +61 3 5732014  Fax: +61 3 5732745
----------------------------------------------------------------------