[rohc] Minor correction in the RFC 3095 implementer's guide

Ghyslain pointed out that section 7.1, as currently written, do
not take into consideration how contexts for connection-oriented
flows can be discarded when the end-to-end connection is closed.
Since the intent with that section was to be profile-independent,
I have therefore rewritten section 7.1 with this in mind:

--------------------------------------------------------------
7.1. Compressor and decompressor MUST keep MAX_CID contexts

  As part of the negotiated channel parameters, compressor and
  decompressor have through the MAX_CID parameter agreed on the
  highest context identification (CID) number to be used. By
  agreeing on MAX_CID, both compressor and decompressor also
  agrees to provide memory resources to host at least MAX_CID+1
  contexts, and an established context with CID within this
  negotiated space MUST be kept by both compressor and
  decompressor at least until either the CID gets re-used, the
  end-to-end connection is closed (connection-oriented flows
  only), or the channel is taken down or re-negotiated.
--------------------------------------------------------------

BR
/L-E

-----------------------------------
Lars-Erik Jonsson, M.Sc.
Senior Research Engineer
Wireless IP Optimizations
AWARE - Advanced Wireless Algorithm Research
Ericsson Research, Corporate Unit
Ericsson AB
Box 920, S-971 28 Luleå, Sweden
E-mail: lars-erik.jonsson@ericsson.com                      /"\
Phone: +46 8 404 29 61                                      \ /
Fax: +46 920 996 21               ASCII Ribbon Campaign      X
Home: +46 8 501 64 503         against HTML email & vCards  / \

My opinions are my personal opinions and should not be considered
as the opinions of my employer, if not explicitly stated.

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