[rohc] non-default capabilities

Hi Learned Authors, Folks,
    I note that the new versions of the drafts (extended and the grand 
unified draft
SigComp-04) draft *are* available, via links on the charter page; I didn't see
ietf-announce messages for these, but they are there.

Having had a (very) quick look at the SigComp draft, I don't see how 
the capabilities
for non-default algorithms are supported - these were discussed on 
the list recently,
but how does an end point report the algorithms it supports (i.e. the 
states it has
available) to its peer (remote) entity?

I ASSUME that there will be a default, mandatory unencumbered 
algorithm that is known
to be supported and so this doesn't need to be reported; for the 
others, however...

Thus, a question - why is this not mentioned in the SigComp draft?
(or is it, in which case, where?).

all the best,
   Lawrence
-- 
lwc@roke.co.uk: +44 1794 833666::<my opinions>:

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