Re: [core] draft-becker-core-coap-sms-gprs-06: Identifying CoAP PDUs

Markus,

I know that the WAP (UDH) is being used for SMS in various applications. I think it's the same as what that is in RFC7925/A.3.
If possible we would like to see this option in the draft to handle existing applications.

BR,
Tim

-----Original Message-----
From: Becker Markus [mailto:Markus.Becker@tridonic.com] 
Sent: Tuesday, March 21, 2017 2:42 PM
To: Carsten Bormann <cabo@tzi.org>; Lauri Piikivi <Lauri.Piikivi@arm.com>
Cc: core <core@ietf.org>
Subject: Re: [core] draft-becker-core-coap-sms-gprs-06: Identifying CoAP PDUs

Hi.

> > The SMS bearer was supported by WAP, way back — hesitate to admit 
> > that
> I worked on it :)  There the assumption was to use the 
> User-Data-Header for ports information, and the assumption was that 8-bit SMS is commonplace.
>
> One of the things that came up during development of this draft is 
> that 8-bit SMS actually is slightly less common than we assumed.  
> Hence the discussion of 7-bit mappings.

At least back in 2014/15 we had troubles doing 8bit SMS with Android. It seems nowadays it should be possible:

http://codetheory.in/android-sms/

https://developer.android.com/reference/android/telephony/SmsManager.html#sendDataMessage(java.lang.String, java.lang.String, short, byte[], android.app.PendingIntent, android.app.PendingIntent)

The Android API seems to give access to the port (==protocol identifier?):
void sendDataMessage (String destinationAddress,
                String scAddress,
                short destinationPort,
                byte[] data,
                PendingIntent sentIntent,
                PendingIntent deliveryIntent)

> > Could the spec refer to WAP directly?
> http://www.openmobilealliance.org/tech/affiliates/wap/wap-259-wdp-
> 20010614-a.pdf
>
> If we can avoid that…
>
> I don’t think implementations right now have a multiplexing point here.
> That would be nice to have to make CoAP over SMS usable with devices 
> such as smartphones.
> I’m just not sure how to do this in a way that accommodates existing 
> implementations.
>
> Grüße, Carsten
>
> _______________________________________________
> core mailing list
> core@ietf.org
> https://www.ietf.org/mailman/listinfo/core
________________________________________________________ The contents of this e-mail and any attachments are confidential to the intended recipient. They may not be disclosed to or used by or copied in any way by anyone other than the intended recipient. If this e-mail is received in error, please immediately notify the sender and delete the e-mail and attached documents. Please note that neither the sender nor the sender's company accept any responsibility for viruses and it is your responsibility to scan or otherwise check this e-mail and any attachments.