Re: [Int-area] What is in a name - draft-ietf-intarea-schc-ip-protocol-number

[Robert Moskowitz <[e-mail]>]

Joe,

You are most likely right.  But it is others in SCHC that requested 
this, so they get to do the justification, or it gets pruned from the ID.

But I will counter that IPsec/HIP/ESP have specific firewall traversal 
mechanisms.  These are examples and I don't know how this is going to 
play out in an IPv6 firewall.

Someone else gets to figure that out...  :)

Bob

On 4/10/23 00:17, [e-mail] wrote:
> Hi, Bob,
>
> Having SCHC as an IP protocol number is more than sufficient to use it 
> with numerous tunneling protocols and/or layering protocols, including 
> GRE - which can be tunneled in UDP too.
>
> Why is that - any of numerous other network-layer tunnel protocols 
> (that demux on network protocol ID)  - not sufficient?
>
> If not, IMO the doc would need to provide the details of the tunneling 
> protocol at the transport layer to justify a transport port assignment.
>
> Joe
>
> —
> Dr. Joe Touch, temporal epistemologist
> www.strayalpha.com
>
>> On Apr 9, 2023, at 2:30 PM, Robert Moskowitz 
>> <[e-mail]> wrote:
>>
>> Joe,
>>
>> My original use case was for SCHC as an IP Protocol Number with 
>> diet-esp being the sample.  WIthout this we have to do a hack on the 
>> SPI management.
>>
>> My more recent work definitely benefits from SCHC as an Ethertype.
>>
>> My text does/will cover these use cases for why.
>>
>> SCHC as a port number was added by others, primarily Pacal Thubert 
>> for UDP firewall traversal.  He will be providing the text for that 
>> use case.
>>
>> Back to writing on this bumpy train ride...
>>
>> Bob
>>
>> On 4/6/23 00:13, [e-mail] wrote:
>>> Hi, Bob,
>>>
>>>> On Apr 5, 2023, at 4:22 AM, Robert Moskowitz 
>>>> <[e-mail]> wrote:
>>>>
>>>> I am in the process of reving draft
>>>>
>>>> draft-ietf-intarea-schc-ip-protocol-number
>>>>
>>>> and adding support for schc as an ethertype and tcp/udp port number 
>>>> as I said I would do back in Nov.  Sigh.
>>>
>>> I understand maybe Ethertype (though I think this is the mistake 
>>> that IPv6 made all over again), but for this to get a port number it 
>>> would need to be associated with a transport service, not just a 
>>> packet type.
>>>
>>> Why would that be needed, e.g., vs. running this inside one of any 
>>> of the numerous transport tunneling protocols (esp GRE)?
>>>
>>> Joe
>>>
>>> —
>>> Dr. Joe Touch, temporal epistemologist
>>> www.strayalpha.com
>>>
>>
>