failed submissions

[cindymorgan]

Describe the issue

To: [email protected] From: "Michael Richardson" [email protected] Date: Sun, 04 Aug 2024 17:00:08 -0400 Subject: failed submissions

While attempting to upload draft-ietf-opsawg-pcap-04, draft-ietf-opsawg-pcaplinktype-04 and a third pcapng document (not yet attempted), I'm getting:

• curl -sS -D versioned/.draft-ietf-opsawg-pcaplinktype-04.upload -F [email protected] -F xml=@versioned/draft-ietf-opsawg-pcaplinktype-04.xml https://datatracker.ietf.org/api/submission curl: (55) Failed sending data to the peer make: *** [lib/upload.mk:27: versioned/.draft-ietf-opsawg-pcaplinktype-04.upload] Error 55 make: *** Deleting file 'versioned/.draft-ietf-opsawg-pcaplinktype-04.upload'

When I repeated for pcap-04, it said:

{"error": "Validation Error", "messages": ["A submission with same name and revision is currently being processed. <a href="/submit/status/144825/">Check the status here."]}+ echo

and I got the confirmation email, and it worked.

I can't seem to do the same for pcaplinktype-04, but I'll try posting the XML through the DT now.

--

From: "Michael Richardson" [email protected] To: [email protected] Subject: Re: [rt5.ietf.org #34978] AutoReply: failed submissions Date: Sun, 04 Aug 2024 17:01:27 -0400

IETF Support via RT [email protected] wrote: Hide quoted text

and I got the confirmation email, and it worked.

Hide quoted text

I can't seem to do the same for pcaplinktype-04, but I'll try posting the XML through the DT now.

When I tried through DT, it said it was already being processed.

--

Subject: Re: [rt5.ietf.org #34978] AutoReply: failed submissions Date: Sun, 04 Aug 2024 18:40:11 -0400 From: "Michael Richardson" [email protected] To: [email protected]

I don't know if this is helpful.

obiwan-work/opsawg/pcapng mcr 10058 %curl -v -sS -D versioned/.draft-ietf-opsawg-pcapng-02.upload -F [email protected] -F xml=@versioned/draft-ietf-opsawg-pcapng-02.xml https://datatracker.ietf.org/api/submission

• Trying [2606:4700::6810:2d63]:443...
• Connected to datatracker.ietf.org (2606:4700::6810:2d63) port 443 (#0)
• ALPN: offers h2,http/1.1
• TLSv1.3 (OUT), TLS handshake, Client hello (1):
• CAfile: /etc/ssl/certs/ca-certificates.crt
• CApath: /etc/ssl/certs
• TLSv1.3 (IN), TLS handshake, Server hello (2):
• TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
• TLSv1.3 (IN), TLS handshake, Certificate (11):
• TLSv1.3 (IN), TLS handshake, CERT verify (15):
• TLSv1.3 (IN), TLS handshake, Finished (20):
• TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
• TLSv1.3 (OUT), TLS handshake, Finished (20):
• SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
• ALPN: server accepted h2
• Server certificate:
• subject: CN=ietf.org
• start date: Jul 30 02:42:38 2024 GMT
• expire date: Oct 28 02:42:37 2024 GMT
• subjectAltName: host "datatracker.ietf.org" matched cert's "*.ietf.org"
• issuer: C=US; O=Let's Encrypt; CN=E5
• SSL certificate verify ok.
• using HTTP/2
• h2h3 [:method: POST]
• h2h3 [:path: /api/submission]
• h2h3 [:scheme: https]
• h2h3 [:authority: datatracker.ietf.org]
• h2h3 [user-agent: curl/7.88.1]
• h2h3 [accept: /]
• h2h3 [content-length: 193329]
• h2h3 [content-type: multipart/form-data; boundary=------------------------3d08092c21291cbc]
• Using Stream ID: 1 (easy handle 0x55695a3690a0) Show quoted text
• TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
• TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
• old SSL session ID is stale, removing
• Connection #0 to host datatracker.ietf.org left intact curl: (55) Failed sending data to the peer

@mcr

Code of Conduct

• [X] I agree to follow the IETF's Code of Conduct