[AVTCORE] SCIP Draft

Begin forwarded message:

> From: Michael.Faller@gd-ms.com
> Date: July 27, 2021 at 11:23:46 AM PDT
> To: bernard.aboba@gmail.com, jonathan.lennox42@gmail.com
> Subject: SCIP Draft RFC  [rt.ietf.org #299766] Forward of moderated message
> 
> 
> Hi,
> I apologize in advance for bothering you with might seem to be trivial questions, but navigating the IETF RFC process is new to us.  With 36 years of engineering, I am not new to processes, but new to IANA and IETF processes. 
>  
> My colleagues and myself were tasked by the SCIP Working Group to create and submit a draft RFC.  I should take a minute to provide a few lines about SCIP.  The draft RFC is brief and the intro sections of that draft covers a lot. But, for here, the SCIP Working Group grew out of a U.S. effort to define and promote an interoperable application layer security protocol; originally for modem-based connections and then IP.  It started in the early 1990s and went international in late 1990s.  it is used by the U.S., NATO, and NATO partners for government/tactical communications.  There is also a some commercial products that I know use it.  I have supported secure communications using SCIP for 28 years. It has a set of standards; and continues to grow.  But, it begins with the media referenced in the draft RFC
> We began working with IANA by registering the sub media type “scip” under Audio and Video media types.  Once that was completed, we submitted the draft RFC. 
> We waited 3 months. No comments were posted. We started to wonder how this works next given we are about 90 days into the 180 days.  Below is my email basically asking, “what happens next?” along with the reply.
>  
> -------- begin original email-7/19------
> My colleagues (Dan Hanson and Keith Maver) and I submitted a draft RFC in April.  https://datatracker.ietf.org/doc/draft-scip-payload/
> As of today, we have not received any comments on the draft. 
> 
> We produced the draft at the request on the SCIP International Working Group and have been asked by them if there is any news on the drafts progress.  There are products in the field that support the protocol and the community wants to approach COTS OEM of network equipment to support the protocol.  The RFC will help with that effort.
>  
> We are wondering what happens if at the end of 180 days not comments have been received. 
> Is there  document that describes what happens next if no comments are received?  
>  Thank You,
> -------- end original email-------
>  
> -------begin IETF reply 7/23--------  
> Hi Michael,
> Unfortunately, the IETF does not have a document that states what happens if no comments were received on a draft as there are numerous of drafts being uploaded each day. But to help facilitate some comments, we suggest that you ask for feedback on your draft by sending an email to the ietf@ietf.org mailing list. This mailing list is used for IETF related discussions, please feel free to read more about the mailing list, here:
> https://www.ietf.org/mailman/listinfo/ietf.
>  
> Alternatively, depending on what area your work falls under, you can also email Working Group Chairs or the responsible Area Directors and ask for feedback (https://datatracker.ietf.org/wg/).
>  
> Best,
> Jenny Bui
> IETF Secretariat
> ---------- end IEFT reply --------
>  
> Jenny, from IETF, provided a path to ‘find’ you, but she did not provide an answer.
> I honestly do not expect much in the way comments. I would be surprised if we did get something outside of a formatting or type issue.
>  
> What happens if no comments are received?   Does the draft RFC get accepted and given a reference number?  If not, then  what is next?
>  
> Call if it is easier.
> Thanks
>  
> Michael Faller
> Senior Principal Systems Engineer
> GENERAL DYNAMICS Mission Systems
> michael.faller@gd-ms.com
> MSIA, CISSP
> 781-410-9336 office / voice mail
> 781-410-9836 lab
> 
> This message and/or attachments may include information subject to GDC4S S.P. 1.8.6 and GD Corporate Policy 07-105 and are intended to be accessed only by authorized recipients.  Use, storage and transmission are governed by General Dynamics and its policies. Contractual restrictions apply to third parties.  Recipients should refer to the policies or contract to determine proper handling.  Unauthorized review, use, disclosure or distribution is prohibited.  If you are not an intended recipient, please contact the sender and destroy all copies of the original message.
>  
>  